Contribution records
Contributors

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

Give credit to everyone
binford2k binford2k
nancydru nancyw
savioret savioret
donquixote donquixote
nedjo nedjo
mudbone91 mudbone91
dpatte dpatte
bribiz bribiz
verta verta
Miria Miria
idcm idcm
mdowsett mdowsett
kardave kardave
seancorrales droidenator
izmeez izmeez
stenjo stenjo
shunshifu shunshifu
queenbeenz queenbeenz
jaybhancock jaybhancock
fnikola fnikola
jlea9378 jlea9378
ralph.dd ralph.dd
Jim Ruby Jim_Ruby
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.