Contribution records
Draft
Contributors

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

Give credit to everyone
jaxxham jaxxham
minoroffense minorOffense
cthiebault cthiebault
tecjam tecjam
zambrey zambrey
srsbl srsbl
asdLArs asdLArs
dealancer vackar
xcono xcono
aetxebeste aetxebeste
mrharolda haroldmadcap
acouch acouch
achton achton
altrugon altrugon
geerlingguy geerlingguy
danylevskyi danylevskyi
carlhinton CarlHinton
mallezie mallezie
petednz petednz
saltednut saltednut
dsnopek dsnopek
sgdev ron_s
nikunjkotecha nikunjkotecha volunteering organization(s): Axelerant
guypaddock guypaddock organization(s): RedBottle Design, LLC customer(s): Inveniem
steinmb steinmb
stewsnooze stewsnooze
drunken monkey drunkenmonkey volunteering
Hagay Hagay
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.