Read the merge flow configuration from file

[f-alizada]

Changes made

• Introduce the step to read the configuration from the json file which should be presented in repository.
• The name and the path of the cofiguration file is configurable
• The workflow parameters changed to have config_file_path and configuration_file_branch

Reason of changing the flow

To improve UX to onboard and create the configuration

Configuration example

{
    "merge-flow-configurations": {
        // The key of the object is source branch
        "release/8.0.3xx": {
           // The branch to which PR should be created
            "MergeToBranch": "release/8.0.4xx",
            // extra switches similar to the https://github.com/dotnet/versions/blob/main/Maestro/subscriptions.json file
            "ExtraSwitches": "-QuietComments"
        },
        "release/8.0.4xx": {
            "MergeToBranch": "main",
            "ExtraSwitches": "-QuietComments"
        }
    }
}

Workflow file example

name: Usage of Inter-branch merge workflow
on: 
  push:
    branches:
      - 'main'
      - 'releases/**'

permissions:
  contents: write
  pull-requests: write

jobs:
  check-script:
    uses: dotnet/arcade/.github/workflows/inter-branch-merge-base.yml@main
    with:
      configuration_file_path: '.config/merge-flow.json'

Checks

The configuration reading step was tested here:

• https://github.com/f-alizada/sdk/actions/runs/9496551424/job/26171197494
• https://github.com/f-alizada/sdk/actions/runs/9496473279/job/26171131885

[mmitche]

I'm fine with the config file being read from one script, then calling the second script. To me that feels more modular.