Issue
Contribution records
Contributors

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

Give credit to everyone
pwolanin volunteering organization(s): Acquia, SciShield
xjm organization(s): Acquia
alexpott volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
oadaeh
catch organization(s): Third and Grove
Crell volunteering organization(s): Palantir.net
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios), Tag1 Consulting, Inc. customer(s): Drupal Association
twistor
webchick organization(s): Acquia
johnshortess volunteering organization(s): 4Site Studios
kgoel organization(s): Forum One
ohthehugemanatee volunteering
mradcliffe volunteering organization(s): Kosada
mpdonadio organization(s): DiD Agency
jhodgdon
yesct volunteering
effulgentsia organization(s): Acquia
tstoeckler organization(s): erdfisch
swentel
attiks organization(s): Attiks
andypost volunteering organization(s): Skilld
mikeryan organization(s): Virtuoso Performance
dkre
drupalninja99
damienmckenna organization(s): Current
berdir organization(s): MD Systems GmbH
amateescu customer(s): Pfizer, Inc.
wim leers organization(s): Acquia
himanshu-dixit volunteering organization(s): Google Summer of Code
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.