Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
mgifford organization(s): CivicActions, OpenConcept Consulting Inc.
vokiel
larowlan organization(s): PreviousNext
andrewmacpherson volunteering organization(s): Annertech
cosmicdreams
BarisW organization(s): ronder
kattekrab organization(s): Catalyst IT
FredCK
darol100 volunteering
alison volunteering
voleger volunteering organization(s): Drupal Ukraine Community, EPAM customer(s): Drupal Ukraine Community, EPAM
duaelfr volunteering organization(s): Happyculture
mandclu organization(s): Northern Commerce
joshmiller organization(s): Acro Commerce
wrd volunteering
CalamityJen organization(s): University of Minnesota
mpotter organization(s): Phase2
pcate
itmaybejj organization(s): Princeton University
shaal volunteering organization(s): Phase2
damienmckenna organization(s): Current
quietone organization(s): PreviousNext
yesct organization(s): Lullabot customer(s): State of Georgia
wim leers organization(s): Acquia
christopher james francis rodgers
edmund.dunn organization(s): Aten Design Group
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.