Issue
Contribution records
Contributors

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

Give credit to everyone
karing
mtift organization(s): Lullabot customer(s): Georgia Public Broadcasting
sanjayk volunteering organization(s): Material customer(s): Drupal India Association
hansa11 volunteering organization(s): QED42
proeung volunteering
shalinigaur volunteering organization(s): Material customer(s): Drupal India Association
atul4drupal organization(s): Material customer(s): Drupal India Association
kishor_kolekar volunteering organization(s): QED42 customer(s): Drupal India Association
indrajithkb organization(s): Material customer(s): Drupal India Association
brianperry organization(s): Bounteous
sd9121 volunteering organization(s): QED42
komalk organization(s): Material customer(s): Drupal India Association
himanshu_sindhwani organization(s): Material customer(s): Drupal India Association
naresh_bavaskar volunteering organization(s): QED42 customer(s): Drupal India Association
mherchel
kiran.kadam911 organization(s): QED42 customer(s): Drupal India Association
jyotimishra-developer 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.