Issue
Contribution records
Contributors

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

Give credit to everyone
attilatilman organization(s): Cheppers customer(s): GatherContent
podarok organization(s): Drupal Ukraine Community, ITCare, Open Y, QS Quacquarelli Symonds customer(s): Drupal Ukraine Community, Open Y, QS Quacquarelli Symonds
jcnventura organization(s): 1xINTERNET
ankitv18 volunteering organization(s): Acquia
rajeshreeputra volunteering organization(s): Acquia, Shivswarajya Inc.
ameymudras organization(s): Salsa Digital
gambry organization(s): EPAM
berdir organization(s): MD Systems GmbH
tdnshah volunteering
balintpekker organization(s): Cheppers customer(s): Acquia
mglaman organization(s): Acquia
scarer
chr.fritsch organization(s): Thunder
kristen pol organization(s): QuantCDN, Salsa Digital
e.bogatyrev volunteering organization(s): EPAM
martijn de wit organization(s): Ablerz
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.