Contribution records
Contributors

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

Give credit to everyone
yched yched
chx chx
dries dries
eMPee584 empee584
cha0s cha0s
cdale cdale
febbraro febbraro
cburschka arancaytar
zaczek zaczek
c960657 c960657
webchick webchick
j_ten_man jtenman
EvanDonovan evandonovan
splash112 marktonino
joachim joachim
deviantintegral deviantintegral
seworthi seworthi
skylord skylord
jbrown jbrown
karens karens
mykmallett mykmallett
pdrake pdrake
GrumpyPhysicist GrumpyPhysicist volunteering
keith.smith keithsmith
vladimir.dolgopolov vladimir.dolgopolov
damien tournoud damz
gábor hojtsy goba
wim leers wimleers
dave reid davereid
giacomo lozito giacomo lozito
James Andres jamesandres
john franklin franklin
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.