Issue
Contribution records
Contributors

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

Give credit to everyone
chx
neclimdul organization(s): APQC
cilefen
larowlan volunteering
dawehner
twistor volunteering
Crell organization(s): Palantir.net
fabianx volunteering organization(s): Tag1 Consulting, Inc.
znerol
benjy organization(s): CodeDrop
pwolanin volunteering organization(s): Acquia
andypost volunteering organization(s): Skilld
alexpott organization(s): Acro Commerce, Chapter Three (acquired by Kanopi Studios), Thunder
pk188 organization(s): OpenSense Labs
cburschka organization(s): PwC's Experience Center
hchonov volunteering
Mixologic organization(s): Drupal Association
mxr576 organization(s): Pronovix
pdenooijer volunteering
bradjones1 organization(s): Not Vanilla, Inc.
berdir organization(s): MD Systems GmbH
catch organization(s): Third and Grove
mondrake volunteering
xjm organization(s): Acquia
longwave organization(s): Full Fat Things
spokje volunteering
phenaproxima organization(s): Acquia
geek-merlin
ghost of drupal past organization(s): Smartsheet
samuel.mortenson
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.