Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
avolve
WildBill
nicholasthompson
okokokok
xaviercas
Clemens
hongbo
playfulwolf
mrfelton
phdhiren
jcmarco
mczenko
jcruz
klonos
mdih
dinwath
xjm
lort
BenK
crea
doq
finex
servantleader
JimmyAx
dashton
popetardo
TripleEmcoder
venusrising
arski
AdrianB
deg
ralizav
vzsze
iva2k
j0nathan
jrearick
charlesjc
tomsm
nickl
aufumy
euchrid9
awolfey
kekkis
TheDoctor
Guo
quicksketch
roderik
gaelicWizard
dhope
zilverdistel
abaddon
Shadlington
ckng
YK85
jleinenbach
nagiek
przemekz
skolesnyk
splash112
mustanggb
scottatdrake
rburgundy
pawel_r
skizzo
mikl
joelstein
djschoone
frob
danepowell
wizonesolutions
smk-ka
steven jones
a.a.egoroff
tim.plunkett
dave reid
dyke it
vadym.kononenko
jm.federico
john franklin
manuel garcia
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.