Issue
Contribution records
Contributors

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

Give credit to everyone
davyvdb
bkoether
rickvug
max6166
populist
mlncn
scroogie
mkrakowiak
philingle
sreese
quicksketch
dries
attiks
dergachev
kriskd
vasi
Rowanw
IreneKraus
pcorbett
PixelClever
rhache
gerardos
greenskin
designerbrent
1kenthomas
pepemty
Leeteq
nielt
nonsie
danielb
fred0
peacog
kriskhaira
kylebrowning
deviantintegral
attheshow
archimedes
twirlingsky
avpaderno
baroquem
avolve
jabraben
dobe
jonskulski
tommyk
j0rd
chriscohen
seabrawk
spidersilk
davidburns
timhobert
king_mushroom
mcrittenden
scoutbaker
pixelite
tjpatterson
rehos
kwinters
divThis
aiphes
csborg
uberhacker
hixster
9802008
jamesbenison
Jeff Burnz
Mac Clemmens
Gerben Zaagsma
dave reid
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.