Contribution records
Contributors

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

Give credit to everyone
zilla zilla
sprsquish sprsquish
ajayg ajayg
icecreamyou icecreamyou
asak asak
dummas_324324_32 dummas_324324_32
wkmit wkmit
kvvnn kvvnn
dima700 dima700
Allisone Allisone
dc1258 dc1258
mortenson mortenson
apmsooner apmsooner
okday okday
deltab deltab
Ela Ela
nonom nonom
Donaldd Donaldd
rhymeswithcamera rhymeswithcamera
igorik igorik
troyl troyl
imDhaval imDhaval
glitz glitz
NathanM NathanM
langworthy langworthy
rajesh1158 rajesh1158
mrf mrf
allandk allandk
halloffame halloffame
baff baff
kevstav13 kevstav13
Sylense Sylense
Originative Originative
warmth warmth
alex.k alexk
sagar ramgade SagarRamgade
oxford-dev oxford-dev
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.