Contribution records
Contributors

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

Give credit to everyone
drewish drewish
jmstacey jmstacey
aaron aaron
pwolanin pwolanin
quicksketch quicksketch
sun sun
chx chx
axyjo axyjo
dries dries
webchick webchick
c960657 c960657
roychri roychri
hapydoyzer nao
boombatower boombatower
jhodgdon jhodgdon
eMPee584 empee584
clojel clojel
catch catch
giuseppegiache giuseppegiache
dman dman
naught101 naught101
marcoka eanima
joachim joachim
andypost andypost
rfay rfay
anrikun anrikun
pillarsdotnet pillarsdotnet
xjm xjm
moshe weitzman weitzman
sun.core sun.core
dave reid davereid
chadwick wood wickamos
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.