Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
pixelwhip organization(s): Aten Design Group
gabesullice organization(s): Acquia
e0ipso volunteering organization(s): Lullabot
cachesclay
joelsteidl organization(s): Aten Design Group
weri organization(s): Previon Plus AG
fakir22
skyredwang organization(s): Acro Commerce customer(s): The Knot Worldwide
cracu
marysmech organization(s): Freely Agency
attheshow organization(s): Richland Library
eliaspapa organization(s): Tabs & Spaces
andypost volunteering organization(s): Skilld
santerref
wim leers organization(s): Acquia
david strauss
alex dicianu
ghost of drupal past
nils.destoop volunteering organization(s): iO
josh waihi
driskell
catch organization(s): Third and Grove
alexpott organization(s): Acro Commerce, Thunder
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.