Issue
Contribution records
Contributors

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

Give credit to everyone
Sk1Zy
drillprp
pfhsmj0
pacome
dafeder
hefox
byronveale
pmichelazzo
hollyfox
rinasek
pt7481
attisan
jibus
dxkernel
xRoR
draxxdk
maxmendez
mas0h
isimgt
brogdawg
kopeboy
draenen organization(s): Monarch Digital
juagarc4
MaskOta
mooru
darrenthomas888
beautifulmind organization(s): Joshi Consultancy Services
peterpoe volunteering
simonbcfa
jprstoney
feelcreative volunteering
pallavi_sugandhi
Brandon_ST
hanskuiters
_ Mazzhe
lunk rat
Valera Tumash
Todd Young
stefan.r
miguel andrade
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.