Issue
Contribution records
Contributors

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

Give credit to everyone
luizps organization(s): CI&T customer(s): Pfizer, Inc.
intrafusion
dieterholvoet volunteering
savel organization(s): EPAM
Oscaner organization(s): CI&T
alexpott organization(s): Thunder
klonos organization(s): Backdrop CMS
rp7 customer(s): Government of Flanders
nikhil_110 organization(s): Material
smustgrave organization(s): Mobomo
Abhisheksingh27 organization(s): OpenSense Labs customer(s): DrupalFit
sunlix
nod_ volunteering organization(s): Eclipse Foundation
dww volunteering
luenemann organization(s): FlexiFlow GmbH
caminadaf
dev.patrick organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
nikolas.tatianenko organization(s): EPAM
narendra.rajwar27 volunteering organization(s): Material customer(s): Drupal India Association
nitin shrivastava organization(s): OpenSense Labs
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.