Contribution records
Contributors

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

Give credit to everyone
JamesK jkenn99
pwolanin pwolanin
chx chx
sun sun
catch catch
lpalgarvio LPCA
jthorson jthorson
rickmanelius rickmanelius
alexweber alexweber
yktdan yktdan
Topcheese Topcheese
droplet droplet
merlinofchaos merlinofchaos
fago fago
andypost andypost
amateescu amateescu
yareckon yareckon
rfay rfay
xjm xjm
dries dries
danchadwick DanChadwick
Crell Crell
webchick webchick
plach plach
ParisLiakos rootatwc
swentel swentel
johncs johncs
klonos klonos
ghalaat ghalaat
tim.plunkett tim.plunkett
mark trapp itafroma
damien tournoud damz
owen barton grugnog
hass hass
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.