Contribution records
Contributors

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

Give credit to everyone
rszrama rszrama organization(s): Centarro
benstallings BenStallings
kotnik kotnik
sorensong sorensong
Slacker Slacker
XC1 XC1
vasike vasike
quantos quantos
torgospizza torgospizza volunteering
robcarr robcarr
aaronbauman aaronbauman
rkendall rkendall
modctek modctek
camdarley camdarley
rajeevk drupler
deggertsen deggertsen
bisonbleu bisonbleu
guy_schneerson guy_schneerson
andrews501 andrews501
millionleaves millionleaves
capfive capfive
maxplus maxplus
kopeboy kopeboy
chop chop volunteering
mrpeanut MrPeanut
caldenjacobs caldenjacobs
johnpicozzi johnpicozzi organization(s): Oomph, Inc.
bmango bmango
Paintbox Paintbox
kevinsiji kevinsiji volunteering
lisastreeter lisastreeter organization(s): Centarro
selfirian selfirian
yaach yaach
damien tournoud damz
Matt Lewis MattLewis
BenK benk
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.