Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
tedbow organization(s): Acquia
grayle organization(s): Dropsolid
rajandro volunteering organization(s): Material customer(s): Drupal India Association
dravenk volunteering organization(s): Google Summer of Code
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
vsujeetkumar organization(s): Material customer(s): Drupal India Association
NitinLama volunteering organization(s): OpenSense Labs
DonAtt volunteering
thomasdbcklr organization(s): Dropsolid
nginex organization(s): Dropsolid, Drupal Ukraine Community customer(s): Dropsolid
kostyashupenko organization(s): Skilld
anybody organization(s): DROWL.de
matthijs organization(s): Dropsolid
smustgrave organization(s): Mobomo
hitchshock organization(s): DevBranch, Dropsolid, Drupal Ukraine Community
circuscowboy volunteering
sboden volunteering
pjonckiere organization(s): Dropsolid
liquidcms
l_vandamme organization(s): Dropsolid
mahde
rodrigoaguilera organization(s): Dropsolid
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.