Contribution records
Contributors

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

Give credit to everyone
patrickharris patrickharris
rszrama rszrama
lias lias
schnizZzla schnizZzla
dami dami
fhelmschrott fhelmschrott
Luneh Luneh
NewToDruballer NewToDruballer
michelle Michelle
csc4 csc4
spooky69 spooky69
chx chx
plumwd plumwd
Wyze1 wyze1
vijayface vijayface
litwol litwol
oadaeh oadaeh volunteering
boris mann borismann
Christefano-oldaccount christo
. - dot dot
kalashari kalashari
vlip vlip
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.