Issue
Contribution records
Contributors

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

Give credit to everyone
fago
citlacom
sun
themoep
xjm
klausi
catch
nagiek
hnln
firebird
aaronbauman
janchojnacki
ErnestoJaboneta
mcgo
shenzhuxi
jamesfk
michaeldhart
vmd111
unic
7wonders
pluess
FranckV
andrewbelcher
dewancodes
perforator
marcingy
David_Rothstein
mackpipe1
agentrickard
webchick
compa
manuelBS
StoraH
gnucifer
anavrin
kingswoodute
yenidem
anybody
ts145nera
miccil
girishmuraly
dakala
mgifford
nasia123
tstoeckler
Topcheese
cgdrupalkwk
julia_g
jphelan
mvc
bassplaya
crifi
cimo75
zmove
rsole
train
spleshka
steinmb
flocondetoile
Guilro
andypost
ergophobe
pinueve
kris77
Dean Reilly
tim.plunkett
System Lord
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.