Contribution records
Draft
Contributors

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

Give credit to everyone
emptyvoid emptyvoid
arun_ms arun_ms
acidpotato acidpotato
sportel sportel
developer_426 developer_426
waltercat waltercat
donquixote donquixote
loparr loparr
akosipax akosipax
googletorp googletorp
torgospizza torgospizza
joelpittet joelpittet
mdupree mdupree volunteering organization(s): Acro Commerce
msti msti volunteering
arunkumark arunkumark volunteering organization(s): DrupalPartners customer(s): Binary Works
JulienF JulienF organization(s): Eweev LTD customer(s): ShopBuilder
sardis Sardis organization(s): Drupal Ukraine Community, Drupalway customer(s): Drupal Ukraine Community, Drupalway
JorgenSandstrom JorgenSandstrom customer(s): Miss Mary of Sweden
vlad.dancer vlad.dancer organization(s): Drupalway
fadi.assaad fadi-assaad
rszrama rszrama
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.