Contribution records
Contributors

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

Give credit to everyone
dww dww
catch catch organization(s): Third and Grove
chipzz chipzz
anavarre anavarre
sun sun
David_Rothstein drothstein volunteering
xjm xjm
dries dries
mustanggb akamustang
jhodgdon jhodgdon
klausi klausi
c960657 c960657
chuangban2012 chuangban2012
mgifford mgifford
mikeytown2 mikeytown2
kerasai bmoresafety20
patrickd patrickd
sassafrass synsas
dbcollies dbcollies
vladsavitsky vladsavitsky
joates joates
raulmuroc RaulMuroc
fabianx Fabianx volunteering organization(s): Tag1 Consulting, Inc.
john_b John_B
izmeez izmeez
kmonty kmonty organization(s): BKJ Digital
IT Guy 3000 IT Guy 3000
devin carlson DevinCarlson
scott m. sanders scott m. sanders
thomas.fleming thomas.fleming
joseph.olstad joseph.olstad
hass hass
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.