Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
fabianx volunteering organization(s): Tag1 Consulting, Inc.
andypost volunteering organization(s): Skilld
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
toomanypets
catch organization(s): Third and Grove
znerol
m1r1k
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
mile23 volunteering
pk188 organization(s): OpenSense Labs
aleevas organization(s): Skilld
nickdickinsonwilde organization(s): Taoti Creative
baikho volunteering organization(s): Access (now GAIN)
jherencia
effulgentsia organization(s): Acquia
zterry95 organization(s): DAVYIN Internet Solutions / 戴文信息科技有限公司
spokje volunteering
karishmaamin organization(s): Specbee
ankithashetty volunteering organization(s): Specbee
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
smustgrave organization(s): Mobomo
steinmb organization(s): University Of Bergen
wim leers organization(s): Acquia
chris burge
webkings.ca
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.