Issue
Contribution records
Contributors

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

Give credit to everyone
castawaybcn
nancydru
jerdavis
maijs
j0rd
andypost
nhck
pfaocle
hovel
mrfelton
dman
richardtmorgan
mediamash
diederik_2mpact
weseze
9802008
alesr
EmanueleQuinto
vasike
khoomy
psynaptic
Asoahc
nomonstersinme
xurizaemon
robeano
mvc
attiks
stella
zilverdistel
ManyNancy
bricef
srobert72
cedarm
satcom74
skizzo
red18
tjjacobsen
joecanti
kingandy
UNarmed
majdi
timb
karlschneider98
rafaeldwan
aaronbauman
ak
lipcpro
neillodwyer
GaneshKumar
revagomes
DomP
corbin
stijnd
made4w3
d3str0y
beto_beto
vb_swapnil
ñull
dean.p
Justin Miller
goyal.286
asad.hasan
husumiao-1
Nikdhil Mdohfan
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.