Issue
Contribution records
Contributors

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

Give credit to everyone
mpdonadio organization(s): DiD Agency
swatichouhan012 organization(s): Valuebound customer(s): Valuebound
hash6 organization(s): QED42 customer(s): Drupal India Association
jeroent organization(s): iO
vladbo organization(s): EPAM
pifagor volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
adityasingh volunteering organization(s): Material customer(s): Drupal India Association
andypost volunteering organization(s): Skilld
ankithashetty volunteering organization(s): Specbee customer(s): Drupal India Association
mondrake volunteering
quietone organization(s): PreviousNext
jhedstrom organization(s): Phase2 customer(s): Smithsonian Institution
spokje volunteering
daffie
bhanu951 volunteering
viniciusrp organization(s): Open Social
smustgrave organization(s): Mobomo
acbramley organization(s): PreviousNext customer(s): Service NSW
catch organization(s): Third and Grove
kristen pol organization(s): Hook 42
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.