Contribution records
Contributors

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

Give credit to everyone
viktorfransson viktorfransson
mlieshout mlieshout
ambo ambo
andrenoronha andrenoronha
wesjones wesoccer2003
gpk gpk
escoles escoles
samiu1287 samiu1287
neoglez neoglez
zhuoyan zhuoyan
bradweikel bradweikel
nicootje nicootje
guile2912 guile2912
aganz aganz
alexis alexis
edhel edhel
solodky solodky
Josephnewyork Josephnewyork
JThan JThan
mikeytown2 mikeytown2
brunorios1 brunorios1
ergonlogic ergonlogic
kristat kristat
an.droid android
damien tournoud damz
andrew.eatherington@gmail.com Brico
Matt-H Matt-H
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.