Issue
Contribution records
Contributors

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

Give credit to everyone
stomusic
matroskeen volunteering organization(s): DevBranch, Drupal Ukraine Community customer(s): DevBranch
dvanbrenk
marty2081 organization(s): ronder
terranrich
akoe volunteering
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
naheemsays
tostinni organization(s): Agence Propal
thpoul organization(s): Pixual
rasikap organization(s): Material
berdir organization(s): MD Systems GmbH
chemsabd
nitebreed organization(s): Synetic
guptahemant volunteering organization(s): QED42 customer(s): Drupal India Association
megachriz volunteering organization(s): WebCoo
pdxclankeith volunteering
sutharsan organization(s): ronder
fishfree
skylord
fozzieblue organization(s): Nashville Public Library
bramdriesen volunteering organization(s): Sopra Steria
ivnish
cgoffin organization(s): Sopra Steria
lobodakyrylo volunteering
anairamzap organization(s): Mobomo
jvandooren organization(s): Sopra Steria
drupalite1411
rahulk volunteering organization(s): Cognizant Technology Solutions
Tyetho
elijah lynn organization(s): Red Hat
liam mcdermott
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.