Issue
Contribution records
Contributors

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

Give credit to everyone
quicksketch
effulgentsia
Isostar
davidzz
binford2k
steinmb
thekevinday
nateb
igorik
didox
LDawg
tsvenson
mlncn
denniemans
georgedamonkey
BenK
bfroehle
patrickharris
W32
scroogie
nicholasthompson
rodrigoaguilera
tebb
jthomasbailey
sylvain_a
Kama
mortendk
antiorario
wayfarer_boy
cherokeedude
good_man
attiks
l33tdawg
perandre
joostvdl
knaffles
bennash
aristeides
damir
off
mouize
TimG1
pkej
Barfly
luckystrikerin
threading_signals
barobba
mattbk
thoughtcannon
7wonders
joakimekroos
Subbo
electblake
andros
toxiclung
bdunwood
TripX
mavimo
Shadlington
kueblert
jerdavis
robloach
manveru
jeffwidman
Screenack
akagroundhog
rowbotony
boris mann
nicolas.antoniazzi
Scott J
ClaudeS-1
jon betts
agence web coheractio
navid.kashani
dwynne@gmx.de
carlos.macao
basicmagic.net
beltofte
fender-dupe
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.