Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
drupalfan2
ldavidsp organization(s): MTech, LLC
heddn organization(s): MTech, LLC
Munavijayalakshmi organization(s): Valuebound
lendude organization(s): iO, Noctilaris
piggito volunteering organization(s): Skilld
andypost volunteering organization(s): Skilld
jhuhta organization(s): Siili Solutions
dire organization(s): Siili Solutions
jurgenhaas organization(s): bitegra Solutions, LakeDrops
fhaeberle organization(s): bitegra Solutions, PARAGON Executive Services GmbH
quietone organization(s): PreviousNext
mohit_aghera organization(s): PreviousNext
smustgrave organization(s): Mobomo
meeni_dhobale organization(s): QED42 customer(s): Drupal India Association
kriboogh organization(s): Calibrate
useernamee organization(s): drunomics
nicrodgers volunteering
peter.draucbaher volunteering
joseph.olstad
deepak goyal organization(s): Material customer(s): Drupal India Association
the.tai.pen@gmail.com organization(s): JAKALA (formerly FFW)
petar_basic organization(s): drunomics
jonnyhocks
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.