Issue
Contribution records
Contributors

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

Give credit to everyone
karens
aclight
chx
alex_b
eaton
ShawnClark
plach
davidredshaw
markus_petrux
newbuntu
univate
catch
roychri
andremolnar
webchick
joshmiller
threexk
akeimou
brianfisher
sun
dries
robatsu
litwol
scor
westbywest
tomgf
pvasener
effulgentsia
skibum3d
japanitrat
idmacdonald
dunx
chales
xxparanormalxx
kotnik
gausarts
zilverdistel
apanag
jarune
Remon
pdrake
socialnicheguru
nzcodarnoc
incaic
claar
anrikun
moshe weitzman
mugginsoft.net
jody lynn
Island Usurper
nick.dap
aaron.r.carlton
Bodo Maass
Renee S
Dave Cohen
gábor hojtsy
bjaspan
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.