Issue
Contribution records
Contributors

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

Give credit to everyone
kbahey
lilou
arhak
dmitrig01
BartVB
slantview
pwolanin
jeremy
dries
bjaspan
torbjorn
natrio
egbertb
beltofte
Starminder
ismaiel
socialnicheguru
webchick
berdir
c960657
markus_petrux
donquixote
EvanDonovan
aaron
delty
tstoeckler
mark_r
irakli
jmpalomar
febbraro
sun
coltrane
awry
TC44
xtfer
mrfelton
gpk
azinck
andypost
nonsie
Mike_Waters
Viybel
achilles085
gaele
JamesK
SamRose
pimousse98
chrism2671
dalin
rmjiv
rfay
zapscribbles
crea
alanburke
miro_dietiker
domidc
q0rban
bryancasler
kardave
locomo
protoplasm
bcobin
Witch
iva2k
AdrianB
kerberos
srobert72
vacilando
tomceek
freescholar
christefano
kevinquillen
yanyan729
kenorb
plach
damien tournoud
moshe weitzman
gábor hojtsy
Pedro Lozano
Turkish Delight
gerhard killesreiter
dave reid
josh waihi
pixelpreview@gmail.com
Adam S
Carlos Miranda Levy
david strauss
hass
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.