Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rooby
samhassell
pol volunteering
longwave volunteering
markhalliwell organization(s): Tag1 Consulting, Inc.
sgdev
David_Rothstein volunteering
batkor
andypost volunteering organization(s): Skilld
aklump
bmunslow volunteering
neclimdul organization(s): APQC
callen321
quietone organization(s): PreviousNext
_utsavsharma organization(s): OpenSense Labs customer(s): DrupalFit
adinancenci organization(s): Zoocha
jmagunia
bnjmnm organization(s): Acquia
utkarsh_33 volunteering organization(s): Acquia
tim.plunkett organization(s): Acquia
geek-merlin organization(s): MachbarMacher
sahil.goyal volunteering organization(s): Material customer(s): Drupal India Association
yash.rode organization(s): Acquia
donutdan4114
budda
mortona2k
anybody volunteering organization(s): DROWL.de
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.