Contribution records
Contributors

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

Give credit to everyone
julma julma
zmove zmove
sun sun
skizzo skizzo
socialnicheguru SocialNicheGuru
dawehner dereine
ctalley5 ctalley5
esmerel esmerel
joeslow joeslow
merlinofchaos merlinofchaos
slashwalk slashwalk
srsbl srsbl
crutch crutch
pelicani pelicani
bowwowadmin bowwowadmin
capellic capellic
wolfraem wolfraem
EvanDonovan evandonovan
meba meba
mickc MickC
3dloco 3dloco
hawleyal hawleyal
MrMaksimize MrMaksimize
AdrianB AdrianB
jayhariani jayhariani
njim nJim
nigelwhite nigelwhite
glass.dimly glassdimly
R.Hendel RalfHendel
paul.brightlemon paul.brightlemon
greg.harvey greg.harvey
a.milkovsky milkovsky
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.