Contribution records
Contributors

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

Give credit to everyone
sime sime
sammys sammys
kevinwalsh kevinwalsh
WisTex WisTex
jdsaward jdsaward
druvision levavie
p_palmer p_palmer
rdsmith rdsmith
goose2000 goose2000
GravitySpec GravitySpec
Osangar Osangar
brmassa brmassa
syngistic syngistic
marie70 marie70
Nikkol Nikkol
ms2011 mikesmullin
theorichel theorichel
davea davea
Phillip Mc Phillip Mc
decibel.places decibel.places
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.