Contribution records
Contributors

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

Give credit to everyone
naught101 naught101
andrenoronha andrenoronha
upupax upupax
redndahead redndahead
intyms intyms
BenK benk
orbgasm orbgasm
unfeasible unfeasible
rconstantine rconstantine
pdcarto patdunlavey
socialnicheguru SocialNicheGuru
bluestarstudios bluestarstudios
2ndChanceTech 2ndChanceTech
ndwilliams3 ndwilliams3
gobioasis gobioasis
izmeez izmeez
ajayg ajayg
rusmaz rusmaz
dpatte dpatte
alfthecat AlfTheCat
jnettik jnettik
safetypin mcowgur
mcarbone mcarbone
kumkum29 kumkum29
firfin firfin
mefisto75 mefisto75
Wolfgang Reszel Tekl
Steven Brown fatguylaughing
arne.olafson arne.olafson
scott.browne scott.browne
Biswajit Roy biswajitroy22
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.