Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
larowlan organization(s): PreviousNext
chx
xtfer
joelpittet
jibran
dawehner volunteering
fabianx volunteering customer(s): Acquia
jhodgdon
sam152 volunteering organization(s): CodeDrop, PreviousNext
benjy
Crell volunteering
cilefen
xano organization(s): Druid
eric_a
markhalliwell organization(s): Tag1 Consulting, Inc.
phenaproxima organization(s): Acquia
nod_ organization(s): Acquia
mallezie organization(s): iO
bhanu951 volunteering
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
smustgrave organization(s): Mobomo
chi
andypost volunteering organization(s): Skilld
oily volunteering organization(s): Cactus Blossom IT Services Limited
catch organization(s): Third and Grove
pdureau volunteering
tim.plunkett volunteering
kim.pepper organization(s): PreviousNext
star-szr
dave reid volunteering
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
manuel garcia volunteering
ghost of drupal past
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.