Contribution records
Draft
Contributors

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

Give credit to everyone
vierlex vierlex organization(s): acolono GmbH
echo15 echo15 organization(s): EPAM
linichalexey linichalexey organization(s): EPAM
keats76 keats76
legolasbo legolasbo
maacl maacl
cyberwolf Cyberwolf organization(s): 2DotsTwice bvba customer(s): Dropsolid
meanderix meanderix
johnzzon johnzzon organization(s): Kodamera AB
kevinquillen kevinquillen organization(s): Velir
hitchshock HitchShock organization(s): DevBranch, Dropsolid, Drupal Ukraine Community
fjgarlin fjgarlin volunteering organization(s): Drupal Association
bgreco bgreco
hchonov hchonov organization(s): 1xINTERNET
ressa ressa organization(s): Ardea
drunken monkey drunkenmonkey volunteering
das-peter daspeter organization(s): Cando
d.steindl d.steindl volunteering
phjou stargayte
nicrodgers nicrodgers organization(s): Welsh Government
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.