>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3503337. --> Reported by: [jonathan1055](https://www.drupal.org/user/92645) Related to !24 !31 !17 !8 !14 !13 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>This project needs to cover several key set-ups of Contrib projects, to help us increase test coverage. This will need several branches, which may not differ by much. We can use the recognised version naming conventions as in regular contrib projects</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <h4>Testing with Drupal 7</h4> <ol> <li>Branch 7.x-1.x which does <i>not</i> contain a <code>composer.json</code> file</li> <li>Branch 7.x-2.x which <i>does</i> contain a <code>composer.json</code> file</li> </ol> <h4>Testing with Drupal 10</h4> <ol> <li>Branch 3.x - which is also compatible with Drupal 9</li> <li>Branch 4.x - which is only also compatible with Drupal 10+</li> </ol> <p>Within each branch, the <code>.gitlab-ci.yml</code> can define variants to test with the minimum and maximum PHP versions for the core releases being used.</p> <h4>MR testing branches</h4> <p>This issue is closed but the test branches are still used. These can be draft Merge Requests, but also the workflow is now set to run a pipeline if the branch name starts with <strong>3503337</strong> so this avoids the need to create MRs</p> > Related issue: [Issue #3503426](https://www.drupal.org/node/3503426)