>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3503426. --> Reported by: [jonathan1055](https://www.drupal.org/user/92645) Related to !324 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>To improve the Gitlab Templates MR test coverage we have created a project called <a href="https://www.drupal.org/project/gitlab_templates_downstream">Gitlab Templates Downstream</a> which will be designed to cover several structural and configurational scenarios for D7 and D10 modules. See <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/gitlab_templates_downstream/issues/3503337" title="Status: Closed (fixed)">#3503337: Plan for initial codebase</a></span> </p> <p>So far, we have used <a href="https://www.drupal.org/project/keycdn">KeyCDN</a>, <a href="https://www.drupal.org/project/api">API</a> and <a href="https://www.drupal.org/project/decoupled_pages">Decoupled Pages</a> as convenient projects for downstream testing, given that one has to be a maintainer of the downstream project to be able to trigger the pipeline. These will remain as linked projects, but they do not cater for all the cases we need to test. The new project can be designed specifically to fill these gaps.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add the pipelines for all the <a href="https://git.drupalcode.org/project/gitlab_templates_downstream/-/branches">Gitlab Templates Downstream branches</a> into this projects .gitlab-ci.yml so they can be run in MRs</p>