Contribution records
Draft
Contributors

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

Give credit to everyone
dries dries
quietone quietone
ankitv18 ankitv18
znerol znerol
karimb KarimB
oily andrewfarq
smustgrave smustgrave organization(s): Mobomo
lostcarpark lostcarpark volunteering
jberghammer jberghammer
till79 till79
ranzinator2000 ranzinator2000
michael.j.gleeson Michael.J.Gleeson
mradcliffe mradcliffe volunteering organization(s): Kosada
awset awset volunteering organization(s): Salsa Digital
rduterte rduterte
rakesh.regar rakesh.regar volunteering organization(s): Innoraft
sj.suraj sj5515139gmail.com
samlewis samlewis
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.