Issue
Contribution records
Contributors

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

Give credit to everyone
jhedstrom organization(s): Phase2 customer(s): Human Rights Watch, Workday, Inc.
ritzz organization(s): Valuebound
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
rajeshwari10 volunteering organization(s): Valuebound
deepanker_bhalla volunteering organization(s): Material
minakshiPh organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
mahtab_alam organization(s): Valuebound
volkswagenchick organization(s): Kanopi Studios
nvta organization(s): TA Digital
avpaderno volunteering
ridhimaabrol24 organization(s): Material customer(s): Drupal India Association
nitesh624 volunteering organization(s): Material customer(s): Drupal India Association
anabpv organization(s): CI&T
mariaisp organization(s): CI&T
sarguna raj m organization(s): DrupalPartners, Binary Works
govind.maloo organization(s): Salsa Digital
Sourabhagouda SP organization(s): Valuebound
Deepthi kumari volunteering organization(s): TA Digital
drupal.ninja03
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.