Contribution records
Contributors

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

Give credit to everyone
sun sun
kvoltz kvoltz
kjv1611 kjv1611
twod twod
brisath brisath
yan yan
jhedstrom jhedstrom
bncceo bncceo
toodlepip toodlepip
jeffschuler jeffschuler
geerlingguy geerlingguy
herkimer herkimer
mgladding mgladding
droid19 droid19
brei9000 brei9000
jfine jfine
Fannon Fannon
ogi ogi
giorgio79 giorgio79
jdln jdln
webadpro webadpro
jlyon jlyon
ldweeks ldweeks
webengr webengr
bdimaggio bdimaggio
danny englander danny-englander
W.M. Geir19
shiraz dindar Shiraz
R-H R-H
Yaron Tal YaronTal
.kuma .kuma
kappaluppa kappaluppa
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.