Contribution records
Contributors

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

Give credit to everyone
eldrupalista agviu organization(s): Exove
plopesc plopesc organization(s): Cocomore AG
epapaniko epapaniko organization(s): EWORX S.A.
helmo helmo volunteering organization(s): Initfour websolutions
berramou BERRAMOU volunteering
maskedjellybean maskedjellybean
eric_a erica organization(s): Dutch Open Projects, RIVM
audioroger audioroger organization(s): Red Hat
lmlima lmlima2
altcom_neil altcom_nh
petermallett petermallett organization(s): Red Hat
milos.kroulik milos.kroulik
drupal.ninja03 simplybobby
Kojo Unsui kojo
srihari manepally srihari_manepally
ambient.impact Ambient.Impact volunteering organization(s): Consensus Enterprises
iheb.attia ihebattia volunteering
astonvictor AstonVictor volunteering organization(s): Drupal Ukraine Community, DevBranch
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.