Contribution records
Contributors

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

Give credit to everyone
volkswagenchick volkswagenchick organization(s): Kanopi Studios
bmanning81 bmanning81 volunteering organization(s): Current
daggerhart daggerhart
kdassing kdassing volunteering
markie markie
simplyshipley simplyshipley volunteering
weekbeforenext weekbeforenext organization(s): Lullabot customer(s): Georgia Public Broadcasting
arrow Arrow organization(s): Arrow One Solutions
jjmonterey JJmonterey
Widescreen_bob Widescreen_bob organization(s): Current
dobrzyns dobrzyns volunteering
froboy froboy
aloyr aloyr volunteering
clair0917 clair0917
bsnodgrass bsnodgrass organization(s): net2Community, Inc.
hawkeye.twolf derek.deraps organization(s): Lullabot
riff raff mattcws
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.