Issue
Contribution records
Contributors

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

Give credit to everyone
larowlan organization(s): PreviousNext
alexpott organization(s): Acro Commerce, Thunder
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
damiankloip organization(s): Acquia
pacproduct organization(s): Makina Corpus
berdir organization(s): MD Systems GmbH
merilainen organization(s): Mearra (formerly known as Wunder)
brulain
vett
kapetan
mpdonadio organization(s): DiD Agency
whiplashomega
arnoldbird
jacov volunteering
br0ken volunteering organization(s): Drupal Ukraine Community, JAKALA (formerly FFW) customer(s): Drupal Ukraine Community, JAKALA (formerly FFW)
simohell
wim leers organization(s): Acquia
claudiu.cristea volunteering organization(s): Webikon
sorina.hriban
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.