Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
quietone organization(s): PreviousNext
nayana_mvr organization(s): Material
smustgrave organization(s): Mobomo
larowlan organization(s): PreviousNext
bnjmnm organization(s): Acquia
ahsannazir organization(s): QED42
sagarmohite0031 organization(s): QED42 customer(s): Drupal India Association
nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
marc.bau
saurav-drupal-dev volunteering organization(s): Material customer(s): Drupal India Association
hhvardan organization(s): Last Call Media
acbramley organization(s): PreviousNext
ifrik
herved
marcoliver organization(s): IT.NRW
lisotton
dcam
cb_govcms
benjifisher volunteering organization(s): Harvard Web Publishing
robloach organization(s): Kalamuna
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.