Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
cilefen
hardik_patel_12 organization(s): QED42
phenaproxima organization(s): Acquia
aaronmchale
phjou
jidrone organization(s): FlexSite
benjifisher organization(s): FRUITION
sleopold
4kant
ranjith_kumar_k_u organization(s): Zyxware Technologies
mayurngondhkar
jopdebeeck
_utsavsharma organization(s): OpenSense Labs customer(s): DrupalFit
glenndw volunteering
vsujeetkumar organization(s): Material customer(s): Drupal India Association
wannesdr organization(s): VDAB
loze
mahde
OCTOGONE.dev
joseph.olstad
jhandsta organization(s): Anvil customer(s): VDAB
mrinalini9 organization(s): Material customer(s): Drupal India Association
e0ipso volunteering organization(s): Lullabot
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.