Contribution records
Contributors

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

Give credit to everyone
zietbukuel zietbukuel
seppola seppola
saavyone saavyone
korn3lius korn3lius
mittina mittina
droplet droplet
IcanDivideBy0 shurel
omerida omerida
likewhoa likewhoa
jessepinho jessepinho
schnippy schnippy
rudiedirkx rudiedirkx
blogsh blogsh
claira claira
everpat everpat
beezer75 beezer75
norgo norgo
gambry gambry
fago fago
LedZelkin LedZelkin
info@raceeend.nl raceeend
Ole Martin Ole_Martin
John Deefull John_Deefull
nicolas bouteille NicolasBouteille
ahhao ahhao
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.