Contribution records
Contributors

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

Give credit to everyone
bakidok Bakidok
masher masher
xld XLD
hardik_patel_12 Hardik_Patel_12 organization(s): QED42
lendude Lendude organization(s): iO
meladawy Maged volunteering
dmgig dmgig
PeterStubRaindrop PeterStubRaindrop
marcelovani marcelovani organization(s): Atelier7
abedajam abedajam volunteering organization(s): Vardot
golubovicm golubovicm
kartagis Kartagis volunteering
alanin alanin
krina_t krina_t
zarpele GuidoRobertone organization(s): Ocelot
aaronbauman aaronbauman organization(s): Message Agency
bhojwanipankaj05 bhojwanipankaj05 organization(s): TO THE NEW customer(s): TO THE NEW
stephen ollman StephenOllman
vlad.dancer vlad.dancer volunteering organization(s): Drupal Ukraine Community customer(s): Xspace
marco.b marco.b volunteering
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.