Contribution records
Contributors

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

Give credit to everyone
alexpott alexpott
westie westie
sun sun
linl LinL
webchick webchick
aspilicious aspilicious
dries dries
cburschka arancaytar
catch catch
Crell Crell
jthorson jthorson
berdir berdir
chx chx
David_Rothstein drothstein
thedavidmeister thedavidmeister
Letharion Letharion
xjm xjm
effulgentsia effulgentsia
yesct YesCT
mbrett5062 mbrett5062
jibran jibran
juanolalla juanolalla
markhalliwell markcarver
andypost andypost
klonos klonos
Dean Reilly DeanReilly
lars toomre ltoomre
damien tournoud damz
cameron tod cam8001
sylvain lecoy SylvainLecoy
star-szr star-szr
moshe weitzman weitzman
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.