Contribution records
Contributors

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

Give credit to everyone
santam santam
TimelessDomain TimelessDomain
michellezeedru michellezeedru
idmacdonald idmacdonald
arcane arcane
kclarkson kclarkson
imiksu iMiksu
shunshifu shunshifu
NicoB NicoB
elliotttf elliotttf
Sylense Sylense
iamcarrico ChinggizKhan
twistor twistor
ekes ekes volunteering
tallsimon tallsimon
Bensbury Bensbury
edvanleeuwen edvanleeuwen
alfthecat AlfTheCat
drtallsimon drtallsimon
willieseabrook willieseabrook
ngreenup ngreenup
megachriz megachriz volunteering
TravisJohnston TravisJohnston
socialnicheguru SocialNicheGuru
mxr576 mxr576 organization(s): Pronovix
robin monks robinmonks
Jeffrey C. legendm33066
ken hawkins khawkins98
xo xo
bluegeek9 bluegeek9 volunteering organization(s): Knowledge Learning Labs, Portland Webworks
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.