Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
dboulet
fietserwin
amourow organization(s): Fliegen
alex_optim
chrotto
droplet
cslevy
anpolimus volunteering organization(s): Drupal Ukraine Community
mohit1604 volunteering organization(s): Google Summer of Code
sutharsan organization(s): ronder
rafuel92 volunteering organization(s): Ibuildings
kallado volunteering organization(s): JAVALI
mjchadwick organization(s): University of California
TARtech volunteering
Quicksaver
alternativo volunteering
eiriksm organization(s): Ny Media AS, Violinist customer(s): NTNU
jeroent organization(s): iO
ivnish
sebasgd
lo3001
wim leers organization(s): Acquia
shreya shetty volunteering organization(s): Trigyn Technologies Ltd
joao.ramos.costa organization(s): JAVALI
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.