Issue
Contribution records
Contributors

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

Give credit to everyone
chx
mfb
grendzy
tutumlum
sun
Akaoni
xjm
BenK
greggles
rickmanelius
JmsCrk
hanoii
webchick
chaskype
anavarre
zipymonkey
njcheng
coolestdude1
sbandyopadhyay
TheBarnacle
perignon
alexp999
David_Rothstein
frankcarey
kingdee40
krlucas
maen
damienmckenna
Lloyd
jazzdrive3
mgifford
esbon
mbrett5062
pounard
jrviorato
salvis
xlyz
plach
yesct
AntiThesis
DanZ
robloach
beanjammin
Leeteq
mpdonadio
sonicthoughts
mducharme
klonos
luksak
torgospizza
jhrizz
jaredsmith
marioangulo
synth3tk
rbrownell
heddn
catch
mantisae
nerdcore
damiankloip
raphaelhuefner
mikeytown2
amacias
webservant316
mrpeanut
martin107
sanduhrs
znerol
cosmicdreams
dawehner
mikemccaffrey
mausolos
alimac
FrancescoUK
Everett Zufelt
robin monks
mr.baileys
Rick G
star-szr
salah messaoud
paul rowell
Island Usurper
manoj.surala
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.