Contribution records
Contributors

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

Give credit to everyone
sun sun
mikeytown2 mikeytown2
twod twod volunteering
KentK KentK
Filimonov Filimonov
aherok aherok
drupaljohngo drupaljohngo
jhodgdon jhodgdon
dazimon dazimon
brandonratz brandonratz
windtrekker windtrekker
klebar klebar
scottrouse scottrouse
andros andros
hermes14 hermes14
rpruitt625 rpruitt625
kingandy kingandy
barraponto barraponto
jdudziec jdudziec
CarloB CarloB
j0rd j0rd
emackn emackn
WilliamB WilliamB
aaronmeister aaronmeister
summit summit
markbannister markbannister
tstermitz tstermitz
arborrow arborrow
codeyourdream codeyourdream
freibadschwimmer freibadschwimmer
wolfchen wolfchen
tjtj tjtj
dewolfe001 dewolfe001
manu56 manum56
nileema19 nilima.mahadik
scott m. sanders scott m. sanders
Nora McDougall Nora McDougall
venkat-rk venkatrk
asauterChicago asauterChicago
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.