Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
Mixologic organization(s): Drupal Association
mile23 volunteering
catch organization(s): Third and Grove
geerlingguy organization(s): Midwestern Mac, LLC
cilefen organization(s): Institute for Advanced Study
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
anavarre organization(s): Acquia
aaronmchale organization(s): The University of Edinburgh
user1252762
joachim volunteering organization(s): Skunk Works
damienmckenna organization(s): Current
mmjvb volunteering
colan organization(s): Colan Schwartz Consulting, Consensus Enterprises
berdir organization(s): MD Systems GmbH
webchick organization(s): Acquia
hansfn
ndobromirov organization(s): JAKALA (formerly FFW)
jukka792 volunteering
jerdavis organization(s): Horizontal
seanb volunteering
pasqualle volunteering
hart0554 organization(s): University of Minnesota
andypost volunteering organization(s): Skilld
pcate
kartagis volunteering
eric.guerin@ucsf.edu volunteering organization(s): University of California
ghost of drupal past organization(s): Smartsheet
m.stenta
greg.1.anderson organization(s): Pantheon
morbus iff
nevergone volunteering
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.