Issue
Contribution records
Contributors

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

Give credit to everyone
demonde
finex volunteering
markdc
thejimbirch organization(s): Kanopi Studios
maticb
jeroent organization(s): iO
damienmckenna organization(s): Current
bburg organization(s): Forum One
danielveza organization(s): Sparks Interactive
zanvidmar volunteering
justin2pin
oasweb
jwilson3 organization(s): Bluespark
inaw organization(s): Unic
chadmandoo
kclarkson volunteering organization(s): Blend Me, Inc
amaria volunteering
gngn organization(s): Computer Manufaktur GmbH
anybody organization(s): DROWL.de
anruether organization(s): Geeks4Change
pianomansam organization(s): Rapid Development Group customer(s): Christian Reformed Church of America
mxwright volunteering
chandeepkhosa organization(s): 2Toucans
bramdriesen volunteering organization(s): Sopra Steria
pearls
bohus ulrych
jay.dansand
jane_irwin
batkor
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.