Contribution records
Contributors

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

Give credit to everyone
alexpott alexpott organization(s): Acro Commerce
berdir berdir organization(s): MD Systems GmbH
mile23 Mile23
rteijeiro rteijeiro organization(s): 1xINTERNET
marcel66 marcel66 volunteering
mihai11 mihai11
jmikii jmikii volunteering
szloredan szloredan
mairi mairi organization(s): The University of Edinburgh
jibran jibran volunteering organization(s): PreviousNext
mikelutz mdlutz volunteering organization(s): Four Kitchens
voleger voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
plach plach volunteering
jonathan1055 jonathan1055 volunteering
damienmckenna damienmckenna organization(s): Current
catch catch organization(s): Third and Grove
xjm xjm organization(s): Acquia
daniel.bosen daniel.bosen organization(s): Thunder
tim.plunkett tim.plunkett organization(s): Acquia
gábor hojtsy goba organization(s): Acquia
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.