Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
becw organization(s): Palantir.net
Mixologic organization(s): Drupal Association
webchick organization(s): Acquia
mradcliffe organization(s): Kosada
mile23 volunteering
ressa organization(s): Ardea
naheemsays
slasher13 volunteering organization(s): Wolters Kluwer
alexpott organization(s): Acro Commerce, Thunder
nikathone
sic
thursday_bw volunteering
rbeast volunteering
rosk0 organization(s): Catalyst IT
devkinetic
mlncn organization(s): Agaric customer(s): Drutopia, Portside, Teachers with GUTS
douggreen volunteering
stephencamilo volunteering
andypost volunteering organization(s): Skilld
nhoeller volunteering
bramdriesen volunteering
vacho organization(s): Skilld
wheelercreek
crutch
bhanu951 volunteering
cilefen
greg.1.anderson organization(s): Pantheon
shubham.prakash organization(s): OpenSense Labs
ravi.shankar organization(s): OpenSense Labs
frank hh-germany
narendra.rajwar27 volunteering organization(s): Material customer(s): Drupal India Association
anybody volunteering organization(s): DROWL.de
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.