Contribution records
Draft
Contributors

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

Give credit to everyone
p4trizio p4trizio
kevinquillen kevinquillen
longwave longwave
Stevo_0 Stevo_0
kcyarn kcyarn
ambereyes ambereyes
adam_b adam_b
ColinMctavish ColinMctavish
Cablestein Cablestein
kruser kruser
jonathan_hunt jonathanhunt
djdevin devin
scottrigby scottrigby
SeanA SeanA
AllyMediaGroup AllyMediaGroup
fonant Fonant
goodeit goodeit
zviryatko zviryatko
Ricky999 Ricky999
silverwing silverwing
DenimTornado DenimTornado
DanZ DanZ
allexx allexx
rjlang rjlang
Poieo Poieo
petarb PetarB
esquareddesign esquareddesign
tj99ay tj99ay
tgyuksel tgyuksel volunteering
sirish.ayyagari sirish.ayyagari
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.