Issue
Contribution records
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
danflanagan8 organization(s): Horizontal
aleksip
badrange
codebymikey organization(s): Zodiac Media
colan organization(s): Consensus Enterprises
damienmckenna organization(s): Current
damontgomery organization(s): Phase2
edwardchiapet
gnuget volunteering
hanoii
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): Google
joachim volunteering
joelpittet organization(s): The University of British Columbia
kyberman
makazimtingwa
nadavoid organization(s): Phase2
nickdickinsonwilde volunteering organization(s): Taoti Creative
oldspot organization(s): Zoocha
rob230 volunteering organization(s): CTI Digital
StefanPr volunteering
vinodhinisureshbabu
woodseowl organization(s): Cornell University
Git commit message
Commit types
  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.