Contribution records
Contributors

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

Give credit to everyone
rickvug rickvug
lilou lilou
naheemsays nbz
xmacinfo xmacinfo
mcrittenden mcrittenden
cwgordon7 cwgordon7
catch catch
Bojhan bojhan
leisareichelt leisareichelt
webchick webchick
batsonjay batsonjay
dries dries
SeanBannister seanbannister
babbage babbage
linea linea
eojthebrave eojthebrave
David_Rothstein drothstein
erikjohansson erikjohansson
annmcmeekin annmcmeekin
markboulton markboulton
saltcod saltcod
chx chx
kika kika
xano Xano
quicksketch quicksketch
Stefan Nagtegaal Stefan_Nagtegaal
gábor hojtsy goba
todd nienkerk toddnienkerk
damien tournoud damz
Everett Zufelt everettz
alan d. aland
yhahn yhahn
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.