Issue
Contribution records
Contributors

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

Give credit to everyone
sun
berenddeboer
jide
effulgentsia
IceCreamYou2
catch
geerlingguy
plach
oskar_calvo
wojtha
chx
mlncn
bojanz
Bojhan
cweagans
Clean
renat
aspilicious
kika
franz
techczech
tsvenson
ParisLiakos
nickvidal
xmacinfo
robloach
colan
timmillwood
jrowny
arianek
michelle
larowlan
jelle_s
emmajane
nyl_auster
giorgio79
eaton
karschsp
drifter
Crell
carlos8f
naheemsays
eclipsegc
andypost
rainbowarray
dries
rafamd
fubhy
nevergone
valthebald
oseldman
noisetteprod
chi
David_Rothstein
scroogie
DjebbZ
dixon_
Shadlington
nicl
fgm
bleen
TonyK
lelizondo
hgurol
ressa
cpelham
eigentor
Ranko
webchick
philbar
exaboy
js
aaronmchale
lpalgarvio
jonathanshaw
dave reid
henrijs.seso
damien tournoud
rene bakx
owen barton
drunken monkey
jennifer.chang
c-logemann
Richard Archer
sylvain lecoy
j.somers
lars toomre
tim.plunkett
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.