Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
berdir organization(s): MD Systems GmbH
andypost volunteering organization(s): Skilld
catch organization(s): Third and Grove
znerol
almaudoh
dawehner
mgifford organization(s): OpenConcept Consulting Inc.
jibran
richgerdes
hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
avpaderno volunteering
aleevas organization(s): Skilld
janlaureys
casey volunteering organization(s): SWIS
anchal_gupta organization(s): Material customer(s): Drupal India Association
mrinalini9 organization(s): Material customer(s): Drupal India Association
ameymudras organization(s): Salsa Digital
_utsavsharma organization(s): OpenSense Labs customer(s): DrupalFit
vsujeetkumar organization(s): Material customer(s): Drupal India Association
erik frèrejean organization(s): Dutch Open Projects, KennisMeester
ravi.shankar organization(s): OpenSense Labs
eugene.brit
medha kumari volunteering organization(s): Dotsquares Ltd.
prem suthar organization(s): cmsMinds customer(s): Drupal India Association
amateescu customer(s): Tag1 Consulting, Inc.
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.