Issue
Contribution records
Contributors

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

Give credit to everyone
droplet
skottler
gagarine
robloach
plach
gdd
msonnabaum
catch
klausi
rodrigoaguilera
ParisLiakos
fgm
coderintherye
Crell
Topcheese
wizonesolutions
chx
David_Rothstein
mgifford
cweagans
klonos
tstoeckler
skyredwang
xjm
mac_weber
webchick
effulgentsia
sun
jbrown
dawehner
jibran
brianV
cosmicdreams
heddn
BeachsidePaul
amateescu
greggles
xano
twistor
pounard
yannickoo
alexpott
eclipsegc
iantresman
dries
sanguis
yesct
alesr
jthorson
pfrenssen
AimAdvantage
anavarre
Mike Wacker
alan evans
webmaster-eddie
mark trapp
claudiu.cristea
ar-jan
tim.plunkett
alan d.
hass
Git commit message
Commit types
  • 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

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.