Contribution records
Contributors

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

Give credit to everyone
nedjo nedjo
merlinofchaos merlinofchaos
catch catch
Boletus Boletus
nonsie nonsie
sun sun
Bensbury Bensbury
deviantintegral deviantintegral
plach plach
najibx najibx
tomsm tomsm
dagmar dagmar
intyms intyms
dddave dddave
yhahn yhahn
pasqualle pasqualle
ckng ckng
chaps2 chaps2
dawehner dereine
mrwhizkid mrwhizkid
milksamsa milksamsa
jolidog Jolidog
jhedstrom jhedstrom
boobaa boobaa
Bilmar Bilmar
rburgundy rburgundy
spacereactor spacereactor
myxelf myxelf
sagannotcarl sagannotcarl
heatherann heatherann
kotnik kotnik
mokko mokko
Remon rgeorgy
keva keva
summit summit
zualas zualas
YK85 YK85
pol Pol
TripleEmcoder TripleEmcoder
heyyo heyyo
owen barton grugnog
jose reyero reyero
matt v. mattv
greg.harvey greg.harvey
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.