Issue
Contribution records
Contributors

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

Give credit to everyone
ashleyhazle volunteering organization(s): Hogarth Worldwide
jcnventura organization(s): 1xINTERNET
init90 organization(s): Drupal Ukraine Community, ZANZARRA Drupal Agency
spokje organization(s): Annertech
phenaproxima organization(s): Acquia
anas_maw volunteering
mohit_aghera volunteering organization(s): Axelerant
nikunjkotecha volunteering organization(s): QED42 customer(s): Acquia
liampower organization(s): Catch Digital
droodpal volunteering
tanubansal organization(s): Salsa Digital
dww volunteering
danrod volunteering organization(s): esinergia.
amitajgaonkar
heyehren volunteering
aleksi_anisimov volunteering organization(s): Mearra (formerly known as Wunder)
olivier.bouwman organization(s): ThinkShout
norwegian.blue
scot.hubbard
nicolas s.
srihari manepally
edward.peters
avpaderno volunteering
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.