Contribution records
Draft
Contributors

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

Give credit to everyone
strider72 strider72
ericduran ericduran
bowersox brandonojc
mgifford mgifford organization(s): CivicActions, OpenConcept Consulting Inc.
mattyoung mattyoung
nfreear nfreear
casey casey
jensimmons jensimmons
eaton eaton
avpaderno avpaderno
alanburke alanburke
mfer mfer
kika kika
sun sun
fago fago
robloach robloach
webchick webchick
grendzy grendzy
moonray moonray
dave reid davereid
damien tournoud damz
Everett Zufelt everettz
Jeff Burnz jmburnz
will_in_wi willinwi
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.