>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3518579. --> Reported by: [jonathan1055](https://www.drupal.org/user/92645) Related to !346 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>This issue gathers together several changes to the main.yml and main-d7.yml file that should not affect the functioning of any jobs. They relate to presentation of log output, syntax, organisation within the files and forgotten alignment/backports to the D7 template. There are five proposed changes.</p> <h3 id="summary-proposed">Proposed Changes</h3> <ol> <li>Wrap <code>composer install</code> and <code>*require-drush</code> into a collapsed section. This is a big part of the log, but very often we have to scroll over to find the details we are looking for. Having it in a collapsed section makes the log more easily navigable.</li> <li>Remove the deletion of 'parallel' in test-only changes for D7. This was done for D10, but forgotten and not backported to main-d7.yml.</li> <li>The jobs in the file are generally grouped by their stage, we have all the build jobs, then the validate jobs then the test jobs. 'upgrade status' is a test job, it extends 'testing-job-base', but is placed in the middle of the validation jobs. This needs to be moved in the file.</li> <li>Consistency in 'extends:' and 'needs:' syntax. There are 38 "extends:" in the main file which have the full value on the same on same line, which helps when seaching a file to highlight every 'extends:' as you can see what element it extends. There are just 5 which have the syntax split over two lines, which means your editor's 'find all' does not show what the job is extending. Similarly for the "needs:" syntax, some are on one line, some are split over two lines.</li> <li><code>.check-composer-end-code</code> does not need to print the exit code when all is ok and the code is 0. Only print it when there is a problem.</li> </ol> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>