Contribution records
Contributors

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

Give credit to everyone
pixelsweatshop nicoz
chrisroditis chrisroditis
Anticosti Anticosti
dremy dremy
BenK benk
minnur minnur
storyleader storyleader
JGO JGO
mrconnerton mrconnerton
fago fago
pardalman pardalman
refreshingapathy refreshingapathy
the_g_bomb the_g_bomb
carsonw carsonw
ntigh52 ntigh52
rooby rooby
aaronbauman aaronbauman
rszrama rszrama
deggertsen deggertsen
rikki_iki rikki_iki
kebz Kebz
torgospizza torgospizza
nyleve101 nyleve101
metallized sergiomeneses
bjlewis2 bjlewis2
nate.dame nate.dame
josh waihi fiasco
Robin Millette millette
vmi vmi
onsale002 onsale002
tomtech TomTech organization(s): Centarro
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.