feat: change configuration file format

[sileht]

This change changes the configuration format to:

scopes:
  merge_queue_scope: merge-queue
  mode: parallel
  source:
    files:
      js:
        include:
          - "**/*.js"
      python:
        include:
          - "**/*.py"
      other:
        include:
          - "**/*"
        exclude:
          - "**/*.py"
          - "**/*.js"

Sources will later have value like: bazel, nx, turporepo

We will have something like:

scopes:
  merge_queue_scope: merge-queue
  mode: parallel
  source:
    nx:
      command: ["npx", "nx"]

To get the scopes, this will run: npx nx show projects --affected --base={base} --head={head}"

[Copilot]

Pull Request Overview

This PR changes the configuration file format to introduce a hierarchical structure for scopes with nested source configuration. The new format allows for different source types (starting with files) and includes additional fields like mode and merge_queue_scope at the top level of the scopes configuration.

• Restructures configuration format to nest file-based scope definitions under scopes.source.files
• Adds new fields mode and merge_queue_scope to the scopes configuration
• Refactors the match_scopes function to accept file filters directly instead of the full config

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
mergify_cli/ci/scopes/cli.py	Implements new configuration structure with ScopesConfig, SourceFiles, and FileFilters models, and updates the match_scopes function signature
mergify_cli/tests/ci/scopes/test_cli.py	Updates all test cases to use the new nested configuration format and adjusts function calls to match the new match_scopes signature

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 🤖 Continuous Integration

Wonderful, this rule succeeded.

• all of:
  • check-success=test (macos-15)
  • check-success=test (ubuntu-24.04)
  • check-success=test (windows-2025)

🟢 👀 Review Requirements

Wonderful, this rule succeeded.

• any of:
  • #approved-reviews-by>=2
  • author = dependabot[bot]
  • author = renovate[bot]

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 🔎 Reviews

Wonderful, this rule succeeded.

• #changes-requested-reviews-by = 0
• #review-requested = 0
• #review-threads-unresolved = 0

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for c370582.

🟢 All jobs passed!

But CI Insights is watching 👀

[jd]

The format since to implies you could have multiple source which is weird?

[sileht]

The format since to implies you could have multiple source which is weird?

pydantic ensure you can only have one of them.

I struggle to find something where you define the "source" and the source configuration. An alternative would:

mode: serial
source: files
files:
  python:
    include: ["**/*.py"]
    exclude: ["**/autogenerated/*.py"]
    
    
mode: serial
source: nx
nx:
  command: ...

[jd]

The format since to implies you could have multiple source which is weird?

pydantic ensure you can only have one of them.

I struggle to find something where you define the "source" and the source configuration. An alternative would:

mode: serial
source: files
files:
  python:
    include: ["**/*.py"]
    exclude: ["**/autogenerated/*.py"]
    
    
mode: serial
source: nx
nx:
  command: ...

Nevermind, let's keep it that way.

[jd]

Can we default include to *?

Pull request has been modified.