Issue
Contribution records
Contributors

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

Give credit to everyone
aes2
upandrunning
haza
vito_swat
mattyoung
mokko
joachim
Morn
yoroy
geerlingguy
ibex
rolfmeijer
scito
hansfn
RumpledElf
aza101
mightaswell
007pig
bkmarsh
dlampel
Bert386
bryrock
jodeygrist
david71
lloydpearsoniv
pillarsdotnet
bfroehle
tomcatuk
fuzzy76
erdembey
bryancasler
David4514
trobey
Smokie
sun
yched
aspilicious
metamorphmuses
gpk
pgough
richardtmorgan
davedpss
john_b
marcingy
catch
xjm
yurtboy
bleen
swentel
summit
klonos
jtbayly
mpp organization(s): AmeXio Fuse customer(s): District09
j. ayen green
Jamie Holly
Kamal Prasad
lars toomre
alan d.
Tor Arne Thune
tim.plunkett
nils.destoop
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.