Issue
Contribution records
Contributors

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

Give credit to everyone
mrsinguyen
cweagans
a3dse
naught101
aquaseal
pyrello
scottmorgan
ntsieucom
aristeides
cord1
iAutom8
slinco
tronathan
SilviaT
yugongtian
shakty
boombatower
marko42
bomarmonk
spacereactor
bluegeek9
vimalramaka
brightbold
obrienmd
akamaus
JoeEarl69
a_webb
mordonez
JohnnyX
mgregoire83
scarr
somewhere2go
vjcoop
anthonyR
attheshow
timonweb
zkday
jorgeruiz
apatrinos
ergonlogic
NaX
lpalgarvio
madpole
zmeharen
joris_lucius
MacRonin
bachomp
AlanO
oddencreative
ymeiner
Rockettree
lassekt
xatiu
dererik
rodrigoaguilera
jaypark
lefnire
francewhoa
khezer
klonos
chi
hcderaad
basvredeling
attiks
fizk
helmo
Ole Martin
Zohar.Babin
Laith-1
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.