I enjoy keeping my Drupal development skills sharp. One of the ways I do this is through code contributions in various contrib projects like Markdown Easy and Smart Trim . In this quicktip, I'll show you what my typical workflow is when working on a code contribution. Often, working on issue forks and merge requests requires a local copy of the project's Git repository. If the project you're working on doesn't have any Composer dependencies, then the process is generally very straight-forward; just clone the project directly into your web/modules/contrib/ (or similar) directory and you're good-to-go. But, if it does have Composer dependencies, cloning it into the modules/contrib/ directory won't trigger Composer to install dependencies. In this case, I: Create a project-root modules directory. Clone the contrib project into the new modules directory. Modify the composer.json's repositories section as follows: "repositories": { "0": { "type": "path", "url": "./modules/*" }, "1": { "type
PubDate