Contributors

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

Give credit to everyone
baddysonja baddysonja organization(s): 1xINTERNET
volkswagenchick volkswagenchick organization(s): Kanopi Studios
weekbeforenext weekbeforenext organization(s): Lullabot
nickdickinsonwilde NickDickinsonWilde organization(s): Taoti Creative
cambraca cambraca volunteering
raedkhurayji rak2008
kclarkson kclarkson organization(s): Oomph, Inc.
jrearick jrearick organization(s): Iowa State University
leslieg lglynn2299 volunteering
monicadear monicadear
eabquina eabquina volunteering
froboy froboy volunteering
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.