Contribution records
Contributors

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

Give credit to everyone
m3avrck m3avrck
RobRoy robroy
chx chx
robertdouglass robertDouglass
Zen karthik
dries dries
BioALIEN BioALIEN
jonfhancock jonfhancock
webchick webchick
eaton eaton
heine heine
drumm drumm
fago fago
Crimson Crimson
mrgoltra mrgoltra
Fanaile Fanaile
kzuser kzuser
vm vm
james2002 james2002
treksler treksler
optalgin optalgin
oliverpolden xalen
Tromppa Tromppa
Caleb G2 Caleb G2
moshe weitzman weitzman
Stefan Nagtegaal Stefan Nagtegaal
Dinesh Kumar Sarangapani DineshKumar
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.