Issue
Contribution records
Contributors

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

Give credit to everyone
pranit84 volunteering
andypost volunteering organization(s): Skilld
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
sidharthap organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
alexpott organization(s): Acro Commerce, Thunder
kswamy volunteering customer(s): Drupal India Association
damienmckenna organization(s): Current
jenlampton organization(s): Jeneration Web Development customer(s): Metropolitan Transportation Commission
suzymasri organization(s): Pfizer, Inc.
aspilicious
mcdruid organization(s): Acquia
naveenvalecha volunteering
ressa organization(s): Ardea
joshi.rohit100 organization(s): Acquia
kristen pol organization(s): Hook 42
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
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.