Contribution records
Contributors

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

Give credit to everyone
BeaPower BeaPower
chowdah chowdah
taran2l Taran2L
ficklecat ficklecat
jantoine antoinesolutions
pasqualle pasqualle
marktheshark marktheshark
stams24 stams24
Rhodungeon Rhodungeon
rickmanelius rickmanelius
jmornar jmornar
amfriedman amfriedman
JThan JThan
druvision levavie
iwhy cubeer
jeeba jeeba
DanielJohnston DanielJohnston
jramby jramby
iamEAP iamEAP
radimklaska radimklaska
aaronelborg AaronELBorg
manueler manueler
subhojit777 subhojit777
seehive hotouch
dooug dooug
nachiket-1 nachiket-1
Roze-1 legi0nare
ellen.davis davis4104
ezra-g ezrag
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.