Issue
Contribution records
Contributors

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

Give credit to everyone
quicksketch
rho_
xyber
mrfelton
spookypld
jacobson
gumdrop
pyxio
easp
hypatia7777
ankitgoel9999
floretan
sarahjean
doublejosh
jdwfly
alanburke
oerpli
j0nathan
blavish
mcarbone
k74
anfrage
lukspa
chegor
ransom
fridaythe14th
dylanclear
goodboy
amysteen
dayre
sfyn
henrrrik
brianmercer
siteograf
jdlind38
antiorario
sonlinemedia
Dret
plasticlax
magnify
powery
garywiz
jhodnett2
ohyeah
thedark
panamaquono
ceerwk
boazr
Vuds
califken
rolfmeijer
roknrod12
calbasi
cossme
ycwjjjj
fluitfries
crystaldawn
nerdacus
maudik
gamsim
Cadeyrn
pwaterz
pchrosciak
snoman
westsonoma
crifi
jaxxed
gianfrasoft
Jalandhar
sjdavis
smithn.nc
Matt Townsend
marco.1984
matthew petty
Adam S
decibel.places
Sohodojo Jim
marc.groth
Daniel Norton
Jorge Campo
giga-b
snorkers
Git commit message
Commit types
  • 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

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.