Issue
Contribution records
Contributors

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

Give credit to everyone
jhodgdon
abhisekmazumdar volunteering organization(s): QED42 customer(s): Drupal India Association
pratik_kamble organization(s): QED42
kural volunteering organization(s): Cognizant Technology Solutions customer(s): Drupal India Association
vladimiraus organization(s): Tomato Elephant Studio
msuthars volunteering organization(s): QED42 customer(s): Drupal India Association
naresh_bavaskar volunteering organization(s): QED42 customer(s): Drupal India Association
pradeepjha organization(s): Material customer(s): Drupal India Association
alexpott organization(s): Acro Commerce, Thunder
volkswagenchick organization(s): Kanopi Studios
sarvjeetsingh volunteering organization(s): QED42 customer(s): Drupal India Association
meenakshig organization(s): OpenSense Labs customer(s): Drupal India Association
quietone
saurabh-2k17 organization(s): Material customer(s): Drupal India Association
siddhant.bhosale volunteering organization(s): QED42
amber himes matz organization(s): Drupalize.Me
ramya balasubramanian organization(s): Material customer(s): Drupal India Association
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.