Issue
Contribution records
Contributors

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

Give credit to everyone
jaykandari volunteering organization(s): QED42 customer(s): Drupal India Association
alexpott organization(s): Acro Commerce, Thunder
ccjjmartin volunteering organization(s): Four Kitchens
longwave organization(s): Full Fat Things
mglaman organization(s): Centarro
nerdstein volunteering
shaal volunteering organization(s): Palantir.net
vuil organization(s): JAKALA (formerly FFW)
xjm organization(s): Acquia
vladimiraus organization(s): Tomato Elephant Studio
dqd volunteering organization(s): MAROQQO studios
drumm organization(s): Drupal Association
dww
gambry organization(s): manifesto customer(s): University of Dundee
hestenet organization(s): Drupal Association
larowlan organization(s): PreviousNext
mikelutz volunteering organization(s): Four Kitchens
tedbow organization(s): Acquia
tsega organization(s): Axelerant
pingwin4eg volunteering organization(s): Drupal Ukraine Community
gábor hojtsy organization(s): Acquia
kristen pol organization(s): Hook 42
greg.1.anderson organization(s): Pantheon
surabhi-gokte volunteering organization(s): Material customer(s): Drupal India Association
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.