Issue
Contribution records
Contributors

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

Give credit to everyone
nplowman organization(s): JAKALA (formerly FFW)
klemendev volunteering
ao2 volunteering
djg_tram volunteering
paranojik organization(s): Amazee Labs
compugeekpro volunteering
abramm organization(s): DevBranch, Drupal Ukraine Community customer(s): Creative Propulsion Labs
aswathyajish
scalas89
andypost volunteering organization(s): Skilld
rollins organization(s): DevBranch, Drupal Ukraine Community
steinmb volunteering
Ruedische
aviral2809
hchonov organization(s): bio.logis Genetic Information Management GmbH
jeetmail72 organization(s): TO THE NEW
pameeela
serverjohn
rewted
mayurjadhav organization(s): Material
quietone volunteering
Christopher Riley
vadim.hirbu organization(s): JAKALA (formerly FFW)
dmytro-aragorn organization(s): DevBranch customer(s): Creative Propulsion Labs
hass
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.