Contribution records
Contributors

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

Give credit to everyone
Waldknoblauch Waldknoblauch
aocoder aocoder
SNaKeMe SNaKeMe
BenK benk
good_man goodman
chrisgross chrisgross
commanderflash commanderflash
bryrock bryrock
enrikito enrikito
karilu_ec karilu_ec
RedTop RedTop
nambio nambio
Blooniverse the_phi
csedax90 CRY_X2
j4 j4
trillex trillex
SanFeda SanFeda
dynamicdan dynamicdan
juliakoelsch Spry_Julia
mattsmith3 mattsmith3
Rhodungeon Rhodungeon
bedlam bedlam
cobaltje cobaltje
bkosborne bkosborne
fago fago
druderman druderman
henrijs.seso mansspams
Sinan Erdem Sinan_Erdem
rorydflynn rorydflynn
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.