Contribution records
Contributors

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

Give credit to everyone
yched yched
matt2000 matt2000
markus_petrux markuspetrux
danielb danielb
karens karens
rj rj
fgm fgm
likewhoa likewhoa
giorgio79 giorgio79
xkater xkater
colan colan
BenK benk
Remon rgeorgy
naught101 naught101
mlncn mlncn
sun sun
davepoon davepoon
vermo vermo
terminal terminal
cspitzlay cspitzlay
lomo LoMo
sanderc sanderc
LaurentAjdnik LaurentAjdnik
drclaw ceastwood
Neil_in_Chicago Neil_in_Chicago
aidanlis aidan
smls smls
magnus Magnus
scotwith1t phrancescot
aiwata55 aiwata55
manitoba22 manitoba22
steinmb steinmb
sbuts sbuts
zoo33 zoo33
sharikov sharikov
mattiasj mattiasj
keha3912 keha3912
jcarlson34 jcarlson34
rafamd rafamd
bojanz bojanz
rokr rokr
nightowl77 nightowl77
moshe weitzman weitzman
aren cambre arencambre
burt.lo burt.lo
s.daniel s.Daniel
homoludens homoludens
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.