Issue
Contribution records
Contributors

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

Give credit to everyone
meghasharma volunteering organization(s): QED42 customer(s): Drupal India Association
gauravvvv organization(s): OpenSense Labs
spokje
catch organization(s): Third and Grove
lauriii organization(s): Acquia
imalabya organization(s): Specbee customer(s): Drupal India Association
roshanibhangale organization(s): QED42 customer(s): Drupal India Association
mherchel organization(s): Lullabot
hmendes organization(s): CI&T
chetanbharambe organization(s): QED42 customer(s): Drupal India Association
xjm organization(s): Acquia
vikashsoni volunteering organization(s): Zyxware Technologies
smustgrave organization(s): Mobomo
abhijith s volunteering organization(s): Zyxware Technologies
Agnesh Tank organization(s): Acquia customer(s): Acquia
Shubham Sharma 77 organization(s): Material customer(s): Drupal India Association
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
rinku jacob 13 organization(s): Material customer(s): Drupal India Association
asha nair organization(s): Zyxware Technologies
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.