Issue
Contribution records
Contributors

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

Give credit to everyone
shaal volunteering organization(s): Phase2
spokje
cilefen
heddn organization(s): MTech, LLC
alexpott organization(s): Acro Commerce, Thunder
benjifisher volunteering organization(s): FRUITION
aaronmchale
mglaman organization(s): Acquia
neclimdul organization(s): APQC
klonos organization(s): Backdrop CMS
rfay volunteering organization(s): DDEV
longwave organization(s): Full Fat Things
mile23 volunteering
demeritcowboy
catch organization(s): Third and Grove
mikelutz volunteering organization(s): Four Kitchens
chingis
ressa organization(s): Ardea
xjm organization(s): Acquia
nickdickinsonwilde volunteering organization(s): Taoti Creative
masipila volunteering
phenaproxima organization(s): Acquia
damienmckenna organization(s): Current
quietone organization(s): PreviousNext
martijn de wit organization(s): Ablerz
nicolas bouteille
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.