Issue
Contribution records
Contributors

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

Give credit to everyone
adamps organization(s): AlbanyWeb
marcoliver
msti organization(s): zehnplus
berdir organization(s): MD Systems GmbH
andypost volunteering organization(s): Skilld
aditiup
azizos volunteering organization(s): Google Summer of Code
ressa organization(s): Ardea
lmoeni organization(s): IT.NRW
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
suresh prabhu parkala organization(s): Specbee
stefan.korn organization(s): Stefan Korn - Webentwicklung
nick.murza volunteering organization(s): Indrivo
mohammed motar organization(s): Lund University
loon volunteering organization(s): DevBranch, Drupal Ukraine Community, Evolving Web
alyaj2a organization(s): SeeD EM
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.