Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
lokapujya organization(s): Babson College
cilefen organization(s): Institute for Advanced Study
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
msankhala volunteering organization(s): Material
ferrete
lubwn
kapilv volunteering organization(s): Innoraft customer(s): Drupal Association, Drupal Care
vsujeetkumar organization(s): Material customer(s): Drupal India Association
phjou
gauravvvv organization(s): OpenSense Labs
chetanbharambe organization(s): QED42 customer(s): Drupal India Association
kostyashupenko organization(s): Skilld
vikashsoni volunteering organization(s): Zyxware Technologies
smustgrave organization(s): Mobomo
quietone organization(s): PreviousNext
2dareis2do
fgm organization(s): OSInet
subir_ghosh
anybody volunteering organization(s): DROWL.de
stevewilson volunteering
bluegeek9 volunteering
andres.torres
drupal-ramesh volunteering
sarguna raj m volunteering
Madhu kumar volunteering organization(s): Zyxware Technologies
wim leers organization(s): Acquia
andrew answer volunteering
vitaliyb98 organization(s): DevBranch customer(s): DevBranch
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.