Issue
Contribution records
Contributors

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

Give credit to everyone
volkswagenchick organization(s): Kanopi Studios
pirog organization(s): Tandem
mariohernandez volunteering organization(s): Current
areynolds organization(s): Tandem
jenlampton organization(s): Backdrop CMS
jackalope
joshk organization(s): Pantheon
aslaymoore
crswan
smartmonkey
elly
vnmickela volunteering
mcdwayne
oadaeh organization(s): Backdrop CMS, Flatt and Sons
elusivemind
bbujisic volunteering organization(s): Upsun (formerly Platform.sh)
lestat organization(s): EPAM
jkealy volunteering
dinarcon organization(s): Agaric
segovia94 volunteering
schnitzel organization(s): amazee.io
cyberswat organization(s): DDEV
dgorton volunteering organization(s): Pantheon
chaz.chumley
mel-miller
hawkeye.twolf volunteering organization(s): Lullabot
daniel heath
Ron Powell
shawn dearmond organization(s): University of California
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.