Contribution records
Contributors

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

Give credit to everyone
tr tr
Mixologic Mixologic
torgospizza torgospizza
mattsteven mattsteven
flapsjack flapsjack
2dogrc 2dogrc
fragger_fox fraggerfox
dmendo11 dmendo11
sah62 sah62
wkeef wkeef
labtech labtech
jhenry13 jhenry13
redhatmatt redhatmatt
kojis kojis
carwin carwin
charitygrace charitygrace
tomw tomw
infojunkie kratib
jrowny jrowny
joshuautley joshuautley
qrandle qrandle
longwave longwave
Quixote22 Quixote22
SpiesInOrbit SpiesInOrbit
fabianx Fabianx
ergophobe ergophobe
gscerb gscerb
lehket lehket
BigMike BigMike
Desertgirl Desertgirl
ChrisLaFrancis fivefrank
SchwebDesign SchwebDesign
moonleaf moonleaf
rerooting rerooting
ryantdecker ryantdecker
rantee rantee
jimmb jimmb
trrroy trrroy
arne.olafson arne.olafson
mr.andrey mrandrey
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.