Issue
Contribution records
Contributors

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

Give credit to everyone
naoliva
drvdt
david_garcia
johnv
tamonten1
klausi
j_byrd
anybody
maximpodorov
cmedina
wolfshine
Ravenight
oriol_e9g
alesr
toddtomlinson
killua99
ofry
quantos
zabelc
silurius
shi99
mandreato
joaogarin
benjaminarthurt
ispardillo
SilviuChingaru
haggins
kopeboy
mxt
kclarkson
Exploratus
davidneedham
geresy
sashken2
steveoriol
lmeurs
fakir22
jelo
rodrigoaguilera
perignon
bmunslow
jaydee1818
jstoller
danbarron
misthero
d0t101101
zerolab
dawehner
dmegatool
gapple
bbujisic
agileadam
tobiberlin
k.skarlatos
Renee S
cameron prince
W.M.
mike stewart
k.dani
JulienThomas
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.