Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
akasake
jhedstrom organization(s): Phase2
ankithashetty volunteering organization(s): Specbee
daffie
3li volunteering
steinmb volunteering
trickfun
dantonmariano organization(s): Zoocha
solideogloria
smustgrave organization(s): Mobomo
anacona16 organization(s): Agileana
bhanu951 volunteering
smulvih2 organization(s): Cinder Systems Corp. customer(s): OpenPlus
quadrexdev organization(s): DevBranch, Drupal Ukraine Community
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
alexpott organization(s): Acro Commerce, Thunder
diego_mow volunteering organization(s): CI&T
dpi volunteering organization(s): PreviousNext
angrytoast volunteering organization(s): Tableau
roam2345 organization(s): Drupal Connect
tobiasb volunteering
jsutta
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.