Issue
Contribution records
Contributors

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

Give credit to everyone
joelpittet volunteering
slasher13 volunteering organization(s): Wolters Kluwer
skyredwang organization(s): INsReady
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
jibran volunteering
jofitz organization(s): ComputerMinds
xjm organization(s): Acquia
aleevas organization(s): Skilld
andypost volunteering organization(s): Skilld
mfernea organization(s): AmeXio Fuse
markhalliwell organization(s): Tag1 Consulting, Inc.
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
fgm organization(s): OSInet
effulgentsia organization(s): Acquia
catch organization(s): Third and Grove
berdir organization(s): MD Systems GmbH
larowlan volunteering organization(s): PreviousNext
lauriii organization(s): Acquia
webchick organization(s): Acquia
star-szr volunteering organization(s): Northern Commerce
gábor hojtsy organization(s): Acquia
wim leers 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.