Contribution records
Contributors

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

Give credit to everyone
xjm xjm
filijonka filijonka
cdracars cdracars
udaksh udaksh
ZenDoodles ZenDoodles
cweagans cweagans
marcingy marcingy
berdir berdir
catch catch
swentel swentel
danielgmc danielmccosker
dcam dcam
webwarrior webwarrior
martin107 martin107
secretsayan secretsayan
Gaelan Gaelan
dawehner dereine
mrjmd mrjmd
wranvaud wranvaud
David_Rothstein drothstein
chx chx
fasdalf@fasdalf.ru fasdalf-at-fasdalf.ru
star-szr star-szr
joshi.rohit100 joshi.rohit100
rick hood rick02840
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.