Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
mikelutz volunteering organization(s): Four Kitchens
heddn organization(s): MTech, LLC
andypost volunteering organization(s): Skilld
quietone volunteering organization(s): PreviousNext
xjm organization(s): Acquia
larowlan organization(s): PreviousNext
jibran volunteering organization(s): PreviousNext
damienmckenna organization(s): Current
benjifisher organization(s): FRUITION
eclipsegc
neclimdul organization(s): APQC
joachim volunteering organization(s): Factorial.io, TrainingCloud
naveenvalecha volunteering
daffie
kishor_kolekar volunteering organization(s): QED42 customer(s): Drupal India Association
berdir organization(s): MD Systems GmbH
bbrala organization(s): SWIS
tart0 volunteering
smustgrave organization(s): Mobomo
longwave organization(s): Full Fat Things
gábor hojtsy organization(s): Acquia
wim leers organization(s): Acquia
deepak goyal organization(s): Material customer(s): Drupal India Association
tim.plunkett 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.