Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
ranjit1032002 organization(s): Material
urvashi_vora organization(s): Valuebound customer(s): Valuebound
avpaderno volunteering
el1_1el
nitin_lama organization(s): Specbee
paraderojether organization(s): Promet Source
tanuj. volunteering organization(s): Material customer(s): Drupal India Association
sahil.goyal volunteering organization(s): Material customer(s): Drupal India Association
igor mashevskyi organization(s): DevBranch, Drupal Ukraine Community customer(s): Happy Coding
joseph.olstad
zkhan.aamir organization(s): Specbee customer(s): Drupal India Association
a.aaronjake volunteering organization(s): Promet Source
silvi.addweb organization(s): AddWeb Solution Pvt. Ltd. customer(s): AddWeb Solution Pvt. Ltd.
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.