Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
duaelfr volunteering organization(s): Happyculture
mgifford organization(s): CivicActions, OpenConcept Consulting Inc.
andrewmacpherson volunteering organization(s): Annertech
opi volunteering
weekbeforenext organization(s): Lullabot
mikelutz volunteering organization(s): Four Kitchens customer(s): Lullabot
kostyashupenko organization(s): Skilld
pcate
sutharsan organization(s): ronder
vsujeetkumar organization(s): Material customer(s): Drupal India Association
sulfikar_s organization(s): Zyxware Technologies
lauriii organization(s): Acquia
gauravvvv organization(s): Axelerant, OpenSense Labs customer(s): Drupal India Association
quietone volunteering
ankithashetty volunteering organization(s): Specbee
ranjith_kumar_k_u volunteering organization(s): Material, Zyxware Technologies customer(s): Drupal India Association
smustgrave organization(s): Mobomo
wim leers organization(s): Acquia
kentr volunteering
prudloff organization(s): Insite
rkoller
mherchel organization(s): Dripyard
catch organization(s): Third and Grove
larowlan organization(s): PreviousNext
rikki_iki
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.