Contribution records
Contributors

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

Give credit to everyone
berdir berdir organization(s): MD Systems GmbH
Mixologic Mixologic organization(s): Drupal Association
alexpott alexpott organization(s): Acro Commerce, Thunder
andypost andypost volunteering organization(s): Skilld
catch catch organization(s): Third and Grove
dan2k3k4 dan2k3k4 organization(s): Amazee Labs
drumm drumm organization(s): Drupal Association
dww dww volunteering
heddn lucashedding organization(s): MTech, LLC
hestenet hestenet organization(s): Drupal Association
mikelutz mdlutz organization(s): Four Kitchens
voleger voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
xjm xjm organization(s): Acquia
pingwin4eg pingwin4eg volunteering organization(s): Drupal Ukraine Community
gábor hojtsy goba organization(s): Acquia
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.