Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
miro_dietiker organization(s): MD Systems GmbH
nod_ volunteering
berdir organization(s): MD Systems GmbH
kmonty organization(s): BKJ Digital
aspilicious
gantal organization(s): Elevated Third
duwid organization(s): keytec GmbH & Co. KG
phma organization(s): OM
johnrosswvsu organization(s): Promet Source
larvymortera organization(s): Promet Source
nginex volunteering organization(s): Dropsolid, Drupal Ukraine Community
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): Urban Institute
marvil07 organization(s): Tag1 Consulting, Inc.
nicxvan
finex volunteering
camvertiz
jhedstrom organization(s): Phase2
shawn conn organization(s): Luciditi customer(s): BKJ Digital
christian.wiedemann
odai jbr organization(s): Vardot
ahmad khader organization(s): Vardot
papagrande organization(s): VTP Ventures customer(s): Fluke Biomedical
hmdnawaz volunteering
phjou
mpereztejeiro
trafo
vasike organization(s): DEHN digital solutions GmbH
yazanmajadba
hkumar4
ao5357
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.