Issue
Contribution records
Contributors

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

Give credit to everyone
andypost volunteering organization(s): Skilld
hardik_patel_12 organization(s): QED42 customer(s): Drupal India Association
snehalgaikwad volunteering organization(s): QED42 customer(s): Drupal India Association
daffie
heddn organization(s): MTech, LLC customer(s): Google
claudiu.cristea volunteering organization(s): Webikon
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
gábor hojtsy organization(s): Acquia
yedhukrishnan.p@valuebound.com organization(s): Valuebound customer(s): Valuebound
nicxvan organization(s): nLightened Development LLC
quadrexdev volunteering organization(s): DevBranch, Drupal Ukraine Community
berdir organization(s): MD Systems GmbH
catch organization(s): Tag1 Consulting, Inc.
Git commit message
Commit types
  • 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

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.