Contribution records
Contributors

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

Give credit to everyone
roball roball
johnalbin johnalbin
xano Xano
JuliaKM JuliaKM
senpai senpai
nancydru nancyw
sun sun
frankcarey frankcarey
mightyiam mightyiam
dahacouk dahacouk
colinogreen colinogreen
effulgentsia effulgentsia
juan_g juan_g
wwwwoicn wwwwoicn
crosputni crosputni
BenK benk
neokrish neokrish
izkreny izkreny
Dave Cohen yogadex2
damien tournoud damz
Scott Reynolds scottreynolds
aren cambre arencambre
brst t brstt
alan d. aland
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.