Contribution records
Contributors

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

Give credit to everyone
bpinkney bpinkney
jupiterchild jupiterchild
TJM TJM
mattandersondc mattandersondc
jacine Jacine
iameric iameric
akael akael
portait portait
ingopingo ingopingo
mangaan mangaan
yha yha
formalist formalist
sociotech sociotech
_cc_ _cc_
jcmarco jcmarco
jmbarlow jmbarlow
dcarr dcarr
hhkont hhkont
2faroffroad 2faroffroad
willvincent tcindie
pepemty PepeMty
moonray moonray
MacRonin MacRonin
hebhansen hebhansen
cbannerjee cbannerjee
attheshow attheshow
plasticlax plasticlax
jamesoakley JamesOakley
druplicate druplicate
cgrant3d cgrant3d
roball roball
kevancummins kevancummins
matiasc matiasc
ChrisBryant chrisbryant
robin.prieschl robin.prieschl
Jeff Burnz jmburnz
vrajak@gmail.com Vraja
nick_vh nickvh
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.