Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
merlinofchaos
southweb
andypost
Stalski
fourmi4x
sebas5384
rjbrown99
uditmahajan
mojzis
begun
helior
populist
j0rd
anou volunteering
ckng
thsutton
rylynchen
maximpodorov
sjeandroz
eshta
aprice42
parisek
herd45
joshf
a_thakur organization(s): Material
cosolom
mcannon
dmsmidt organization(s): Triquanta
hctom organization(s): undpaul
hkirsman
sean_e_dietrich organization(s): Kanopi Studios
mnico organization(s): TIFON
dave reid
lucas.constantino
m.lebedev
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.