Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
podarok organization(s): ITCare, JAKALA (formerly FFW), Propeople (now part of FFW)
vladbo
bnthms88
raulmuroc
Blumode
infopicard
andypost volunteering organization(s): Skilld
jacov
makbul_khan8 organization(s): Faichi Solutions Pvt Ltd
kaizerking
joachim
mcgovernm volunteering
alabandit volunteering
afi13
mvdve
drupgirl
awasson
nhaarish volunteering
mgifford organization(s): OpenConcept Consulting Inc.
bogdog400 volunteering
mylocaltrades
damienmckenna organization(s): Current
colan organization(s): Colan Schwartz Consulting, Consensus Enterprises
ccjjmartin organization(s): Four Kitchens
eit2103
marc.groth
Melvin Loos volunteering
abhishek-anand organization(s): Acquia
joshua.boltz
wim leers organization(s): Acquia
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.