Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jcnventura organization(s): 1xINTERNET
heddn organization(s): MTech, LLC
jeroent organization(s): iO
hussainweb organization(s): Axelerant
valthebald organization(s): Dropsolid
markdorison organization(s): Chromatic
rodrigoaguilera organization(s): Amazee Labs
RedLucas25 organization(s): Advisor Websites
partyka organization(s): Argonne National Laboratory
larowlan organization(s): PreviousNext
xjm volunteering organization(s): Acquia, xjm
wizonesolutions volunteering organization(s): WizOne Solutions
xmacinfo organization(s): xMac info
fathershawn volunteering
aaronmchale volunteering
rkelbel48 volunteering
damienmckenna organization(s): Current
hansfn
ressa organization(s): Ardea
Mixologic organization(s): Drupal Association
tormi
mile23 volunteering
solideogloria
longwave organization(s): Full Fat Things
moshe weitzman
tim.plunkett organization(s): Acquia
greg.1.anderson organization(s): Pantheon
norman.lol volunteering organization(s): 1xINTERNET
catch organization(s): Third and Grove
phenaproxima organization(s): Acquia
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.