Issue
Contribution records
Contributors

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

Give credit to everyone
andypost volunteering organization(s): Skilld
berdir organization(s): MD Systems GmbH
LKS90 organization(s): MD Systems GmbH
juanse254 organization(s): MD Systems GmbH
naveenvalecha volunteering
pminf
oleksiy organization(s): Skilld customer(s): Drupal Ukraine Community
replicaobscura volunteering organization(s): Top Floor
jibran volunteering
jofitz organization(s): ComputerMinds, jofitz
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
gogowitsch volunteering organization(s): QuoData GmbH Quality & Statistics
mxr576 organization(s): Pronovix
greggles organization(s): Colorado Governor's Office of Information Technology - Colorado Digital Service
adamps organization(s): AlbanyWeb
sja112 organization(s): Material customer(s): Drupal India Association
alexpott organization(s): Acro Commerce, Thunder
shaktik volunteering organization(s): Material customer(s): Drupal India Association
Rkumar volunteering organization(s): Material customer(s): Drupal India Association
jonathanshaw
catch organization(s): Third and Grove
chi
claudiu.cristea organization(s): Webikon
manuel garcia organization(s): Appnovation
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.