Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
gielfeldt
berdir organization(s): MD Systems GmbH
David_Rothstein
rbayliss
effulgentsia
yesct
mikeytown2
catch organization(s): Third and Grove
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios), Tag1 Consulting, Inc. customer(s): Drupal Association
fabianx volunteering organization(s): Tag1 Consulting, Inc.
klausi organization(s): jobiqo - job board technology
geerlingguy volunteering
chx
amateescu customer(s): Pfizer, Inc.
twistor volunteering
bradjones1 organization(s): Not Vanilla, Inc.
ranjith_kumar_k_u organization(s): Zyxware Technologies
damien tournoud organization(s): Centarro
wim leers organization(s): Acquia
ravi.shankar organization(s): OpenSense Labs
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.