Suite merge script

[james-bruten-mo]

PR Summary

Sci/Tech Reviewer: @t00sa
Code Reviewer: @cameronbateman-mo

Initial attempt at a script to merge different git branches for use in suites. The changes have been tested with the LFRic suites and with the lfric_apps rose-stem at vn3.0. If we think this is a good idea I'll also modify the UM suites to use this extraction method to maintain consistency.

These changes allow the dependencies.yaml file to specify multiple branches to merge together. This can be done by:

lfric_apps:
    - source: [email protected]:MetOffice/lfric_apps.git
      ref: 2025.12.1
    - source: [email protected]:james-bruten-mo/lfric_apps.git
      ref: test_merge_branch
    - source: [email protected]:james-bruten-mo/lfric_apps.git
      ref: test_branch2
    - source: [email protected]:james-bruten-mo/lfric_apps.git
      ref: conflic_apps

which will clone the first source and then merge each subsequent source into this. It's currently setup to ignore merge conflicts in rose-stem and dependencies.yaml as these files aren't important for running scientific suites.

Code Quality Checklist

• I have performed a self-review of my own code
• My code follows the project's style guidelines
• Comments have been included that aid understanding and enhance the readability of the code
• My changes generate no new warnings
• All automated checks in the CI pipeline have completed successfully

Testing

• This change has been tested appropriately (please describe)

LFRic standalone suites and lfric_apps rose-stem at vn3.0

Security Considerations

• I have reviewed my changes for potential security issues
• Sensitive data is properly handled (if applicable)
• Authentication and authorisation are properly implemented (if applicable)

AI Assistance and Attribution

• Some of the content of this change has been produced with the assistance of Generative AI tool name (e.g., Met Office Github Copilot Enterprise, Github Copilot Personal, ChatGPT GPT-4, etc) and I have followed the Simulation Systems AI policy (including attribution labels)

Sci/Tech Review

• I understand this area of code and the changes being added
• The proposed changes correspond to the pull request description
• Documentation is sufficient (do documentation papers need updating)
• Sufficient testing has been completed

(Please alert the code reviewer via a tag when you have approved the SR)

Code Review

• All dependencies have been resolved
• Related Issues have been properly linked and addressed
• Code quality standards have been met
• Tests are adequate and have passed
• Security considerations have been addressed
• Performance impact is acceptable

[t00sa]

A handful of suggestions

[t00sa]

Have you considered using the logging module for these instead of printing?