Issue
Contribution records
Contributors

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

Give credit to everyone
mark_fullmer volunteering organization(s): University of Texas at Austin
cosmicdreams organization(s): Velir
hswong3i organization(s): PantaRei Design Limited (Hong Kong)
bradallenfisher organization(s): Pennsylvania State University
timb
trackleft2 volunteering organization(s): The University of Arizona
clayfreeman organization(s): Library Market
quicksketch organization(s): Lullabot
podarok organization(s): Drupal Ukraine Community, ITCare, Open Y, YMCA of the USA customer(s): Drupal Ukraine Community, Open Y, YMCA of the USA
rajan kumar@2026
dave reid volunteering organization(s): Lullabot
daddison organization(s): University of Texas at Austin
murilohp organization(s): CI&T
brahmjeet789 volunteering
rahul_
anicho01
bkosborne
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.