Contribution records
Contributors

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

Give credit to everyone
zakjan zakjan
two40 two40
marcob marcob
dbaumeister dbaumeister
brainski brainski
scottrigby scottrigby
alliax alliax
kyutums kyutums
curagea curagea
grendzy grendzy
aaronshaf aaronshaf
aflores3 aflores3
giorgosk GiorgosK
ikarusweb ikarusweb
ladamiak ladamiak
Afief afief
JubW JubW
fumbling fumbling
doudou doudou
greggles greggles
diamon diamon
ckidow CKIDOW
indytechcook indytechcook
juroon juroon
domineaux domineaux
Christolito Christolito
alex.k alexk
serg.remote serg.remote
Mac Ryan mac.ryan
Mark Theunissen marktheunissen
stijn vanhandsaeme yichalal
yngens snegny
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.