Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jannakha organization(s): Tomato Elephant Studio
cilefen
vladimiraus organization(s): Tomato Elephant Studio
smustgrave organization(s): Mobomo
cafuego organization(s): United Nations
arunkumark volunteering organization(s): Material customer(s): Drupal India Association
herved organization(s): European Commission and European Union Institutions, Agencies and Bodies
tobiasb volunteering
oily volunteering organization(s): Cactus Blossom IT Services Limited
marcin dębicki organization(s): Sopra Steria
usingsession volunteering
dries
alexpott organization(s): Acro Commerce, Thunder
borisson_ organization(s): Calibrate customer(s): Acerta
catch organization(s): Third and Grove
godotislate volunteering
xjm organization(s): Zoocha, xjm
Git commit message
Commit types
  • 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

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.