Contribution records
Contributors

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

Give credit to everyone
sun sun
sampeckham sampeckham
zoo33 zoo33
AmrMostafa alienbrain
twod twod
jofje jofje
mooreds mooreds
portulaca portulaca
that0n3guy that0n3guy
hokuspokus hokuspokus
hoyer hoyer
iko iko
MadtownLems MadtownLems
saml saml
Troodon Troodon
rondev rondev
Ether Ether
wuwei23 wuwei23
monotaga monotaga
mshepherd mshepherd
orbitalpopdog orbitalpopdog
oxen oxen
jaimealsilva jaimealsilva
pennypacker pennypacker
parkview parkview
borngunners borngunners
bentonboomslang bentonboomslang
Reach Reach
vood002 jpez
Snow Valley Consulting Snow Valley Consulting
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.