Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
cilefen organization(s): Institute for Advanced Study
sk33lz organization(s): Zivtech
kunalgautam organization(s): Material customer(s): Drupal India Association
tstermitz
dww volunteering
andypost volunteering organization(s): Skilld
neclimdul organization(s): APQC
gaele
ericgsmith organization(s): Catalyst IT
johnpitcairn
rosk0 organization(s): Catalyst IT
solideogloria
poker10 organization(s): ActivIT s.r.o.
fred6633 volunteering
greggles organization(s): HeroDevs
longwave organization(s): Full Fat Things
gaurav.kapoor organization(s): OpenSense Labs customer(s): DrupalFit
o'briat organization(s): Klee Interactive (Klee Group)
c-logemann organization(s): Nodegard
alexgreyhead
holo96 organization(s): Studio Present
andrii-500
quietone organization(s): PreviousNext
sirclickalot
ressa
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.