Contribution records
Contributors

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

Give credit to everyone
catch catch
mfb mfb
berdir berdir
bfroehle bfroehle
justdave justdave
swentel swentel
mdm mdm
sun sun
cmsproducer iDonny
makara makara
xjm xjm
drewish drewish
thill_ thill
xanchez xanchez
giorgio79 giorgio79
asoqa asoqa
btmash btmash
bvanmeurs bvanmeurs
iamEAP iamEAP
apratt apratt
webchick webchick
drumm drumm
chx chx
kenorb kenorb
turbogeek turbogeek
moshe weitzman weitzman
alan d. aland
damien tournoud damz
jody lynn lynn
clemens.tolboom clemenstolboom
aleksey.tk cyberpunk
Oleksa-1 Oleksa
dave reid davereid
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.