Contribution records
Contributors

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

Give credit to everyone
chx chx
dries dries
Crell Crell
rfay rfay
karens karens
andypost andypost
webchick webchick
aspilicious aspilicious
jpstrikesback jpstrikesback
David_Rothstein drothstein
tutumlum tutumlum
mustanggb akamustang
bjaspan bjaspan
LaurentAjdnik LaurentAjdnik
mfb mfb
jhodgdon jhodgdon
mikl mikl
juanca2626 juanca2626
geerlingguy geerlingguy
ardas duke
kenorb kenorb
damien tournoud damz
josh waihi fiasco
moshe weitzman weitzman
gerhard killesreiter GerhardKillesreiter
greg.harvey greg.harvey
d.novikov d.novikov
m v v m v v
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.