Issue
Contribution records
Contributors

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

Give credit to everyone
alexpott volunteering organization(s): Acro Commerce, Thunder
mondrake volunteering
xjm organization(s): Acquia
berdir organization(s): MD Systems GmbH
voleger volunteering organization(s): Drupal Ukraine Community customer(s): Drupal Ukraine Community, Lemberg Solutions
effulgentsia organization(s): Acquia
xmacinfo organization(s): xMac info
amateescu customer(s): Pfizer, Inc.
heddn organization(s): MTech, LLC
spokje organization(s): Annertech
timmillwood organization(s): Pfizer, Inc.
longwave volunteering
catch organization(s): Third and Grove
mile23 volunteering
fabienly volunteering
fgm volunteering organization(s): OSInet
ghost of drupal past
joseph.olstad
gábor hojtsy organization(s): Acquia
liam morland organization(s): University of Waterloo
ravi.shankar organization(s): OpenSense Labs
gung wang
nils.destoop volunteering organization(s): iO
alex.skrypnyk organization(s): Salsa Digital customer(s): govCMS (Australian Government Department of Finance)
jacob.embree
eugene bocharov volunteering
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.