Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
xjm volunteering organization(s): xjm
phenaproxima organization(s): Acquia
tedbow organization(s): Acquia
johnwebdev
bnjmnm organization(s): Acquia
effulgentsia organization(s): Acquia
rpayanm volunteering organization(s): Kadabra
mrinalini9 organization(s): Material customer(s): Drupal India Association
sanjayk volunteering organization(s): Material customer(s): Drupal India Association
deepakaryan1988 volunteering organization(s): Trigyn Technologies Ltd
arshadkhan35 volunteering
larowlan organization(s): PreviousNext
quietone organization(s): PreviousNext
nivethasubramaniyan volunteering organization(s): Material customer(s): Drupal India Association
bhanu951 volunteering
andypost volunteering organization(s): Skilld
amateescu customer(s): Tag1 Consulting, Inc.
plach organization(s): Tag1 Consulting, Inc.
tim.plunkett organization(s): Acquia
kristen pol organization(s): Hook 42
amber himes matz organization(s): Drupalize.Me
nitin shrivastava 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.