Issue
Contribution records
Contributors

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

Give credit to everyone
antgiant
hswong3i
chx
AjK
jaydub
Susurrus
Crell
alippai
bdragon
dries
pwolanin
kingto
BioALIEN
bjaspan
jgoldberg
recidive
cburschka
catch
magico
theblacklion
beeradb
phpdude
fgm
sun
baldwinlouie
robloach
cfennell
litwol
samirnassar
xaweryz
grub3
alex_b
mfer
sammys
Frando
siromega
cwgordon7
shunting
nielsvm
slantview
AmrMostafa
agentrickard
mikey_p
vikingew
naheemsays
xano
webchick
swentel
dgtlmoon
lilou
olav
CalebD
pasqualle
greggles
wim leers
david strauss
mike booth
keith.smith
gerhard killesreiter
moshe weitzman
Chris Johnson
Jamie Holly
damien tournoud
Garrett Albright
p.brouwers
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.