Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
dww
dpi organization(s): PreviousNext customer(s): Service NSW
bnjmnm organization(s): Acquia
slv_ organization(s): Lullabot customer(s): DocuSign
volkswagenchick organization(s): Kanopi Studios
nishantghetiya volunteering organization(s): QED42 customer(s): Drupal India Association
chetanbharambe organization(s): QED42 customer(s): Drupal India Association
gauravvvv organization(s): Axelerant, OpenSense Labs customer(s): Drupal India Association
vikashsoni volunteering organization(s): Zyxware Technologies
sokru volunteering
utcwebdev organization(s): The University of Tennessee at Chattanooga
smustgrave organization(s): Mobomo
ckrina organization(s): Lullabot
kiran.kadam911 organization(s): QED42 customer(s): Drupal India Association
sakthivel m organization(s): QED42 customer(s): Drupal India Association
abhijith s volunteering organization(s): Zyxware Technologies
chr.fritsch organization(s): Thunder
shweta__sharma organization(s): OpenSense Labs
prashant.c volunteering organization(s): QED42 customer(s): QED42
quietone organization(s): PreviousNext
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.