Contribution records
Contributors

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

Give credit to everyone
Marcodragons Marcodragons
tobiass tobiass
miiimooo miiimooo
masood_mj masood_mj
JennySmith JennySmith
sdboyer sdboyer
bertboerland bertboerland
Christoffer_V christofferv
kidsleep kidsleep
rares rares
raiyne raiyne
Blinkme Blinkme
bomarmonk bomarmonk
sun sun
edrex edrex
drecute charyorde
esmerel esmerel
merlinofchaos merlinofchaos
honorfield honorfield
adamdicarlo adamdicarlo
qpro qpro
Nehbur Nehbur
robin monks robinmonks
matt v. mattv
s.daniel s.Daniel
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.