Contribution records
Contributors

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

Give credit to everyone
kyletaylored KyleTaylored
jibran jibran
ydahi ydahi
pierrelord pierrelord
bradallenfisher baf139
dixon_ dixon
rteijeiro rteijeiro
lavamind lavamind
bwoods bwoods
mailfox mailfox
simone960 simone960
sjbassett sjbassett
pacome pacome
aaronbauman aaronbauman
dealancer vackar
kopeboy kopeboy
stevenx stevenx
nesta_ nguerrero
goldlilys goldlilys
vensires vensires
ean ean volunteering
cyclone321 cyclone321
waqarit waqariz
Berliner-dupe Berliner-dupe
Andre-B baumeier.it
morleman@gmail.com morleman
dom. Miroslav
dwkitchen dwkitchen
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.