Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
mondrake volunteering
chi
longwave organization(s): Full Fat Things
larowlan organization(s): PreviousNext customer(s): Bond University
shadcn organization(s): Chapter Three (acquired by Kanopi Studios)
catch organization(s): Third and Grove
mstrelan
pasqualle volunteering
quietone organization(s): PreviousNext
xjm volunteering organization(s): xjm
mcdruid organization(s): Acquia
markdorison organization(s): Chromatic
andypost volunteering organization(s): Skilld
solideogloria
donquixote volunteering
acbramley organization(s): PreviousNext
wim leers organization(s): Acquia
kim.pepper organization(s): PreviousNext
Git commit message
Commit types
  • 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

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.