Contribution records
Draft
Contributors

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

Give credit to everyone
merlinofchaos merlinofchaos
wuf31 wuf31
cpelham cpelham
kenorb kenorb
pastk pastk
goye2cz goye2cz
Doomd Doomd
palamida palamida
imclean imclean
drecute charyorde
Jokes Jokes
palmaross palmaross
momper momper
nicktech nicktech
anruether anruether
michaeldaly352 michaeldaly352
beifler beifler
summit summit
dqd dqd
BlindWolf8 BlindWolf8
sc0tt30 sc0tt30
nick_t nick_t
japo32 japo32
peacekaat peacekaat
knalstaaf knalstaaf
anrikun anrikun
dawehner dereine
maedi wishstik
David Lesieur davidlesieur
g.rogg g.rogg
shane birley shanebirley
Git commit message
Commit types
  • 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

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.