Skip to content

[proposal] New resolver configuration

87f74e6
Select commit
Loading
Failed to load commit list.
Open

[proposal] New resolver configuration #938

[proposal] New resolver configuration
87f74e6
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Apr 14, 2026 in 1s

5 potential rules

Rule: Add CI label (label)

  • any of:
    • files~=.github/
    • files~=.mdformat.toml
    • files~=e2e/
    • files~=pyproject.toml
    • files~=tests/
    • title~=^ci:
    • title~=^e2e:
    • title~=^hatch:

Rule: Add Mergify label (label)

  • any of:
    • files~=.mergify.yml$
    • title~=^mergify:

Rule: Automatic merge on approval (merge)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • all of:
    • check-success=unit (3.12, 1.75, macos-latest)
    • all of:
      • #approved-reviews-by>=1
    • -draft
    • check-success=e2e (3.12, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest)
    • check-success=e2e (3.12, 1.75, ci_bootstrap_suite, ubuntu-latest)
    • check-success=e2e (3.12, 1.75, ci_build_suite, ubuntu-latest)
    • check-success=e2e (3.12, 1.75, ci_config_suite, ubuntu-latest)
    • check-success=e2e (3.12, 1.75, ci_specialized_suite, ubuntu-latest)
    • check-success=e2e (3.12, 1.75, ci_workflow_suite, ubuntu-latest)
    • check-success=e2e (3.13, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest)
    • check-success=e2e (3.13, 1.75, ci_bootstrap_suite, ubuntu-latest)
    • check-success=e2e (3.13, 1.75, ci_build_suite, ubuntu-latest)
    • check-success=e2e (3.13, 1.75, ci_config_suite, ubuntu-latest)
    • check-success=e2e (3.13, 1.75, ci_specialized_suite, ubuntu-latest)
    • check-success=e2e (3.13, 1.75, ci_workflow_suite, ubuntu-latest)
    • check-success=e2e (3.14, 1.75, ci_bootstrap_parallel_suite, macos-latest)
    • check-success=e2e (3.14, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest)
    • check-success=e2e (3.14, 1.75, ci_bootstrap_suite, macos-latest)
    • check-success=e2e (3.14, 1.75, ci_bootstrap_suite, ubuntu-latest)
    • check-success=e2e (3.14, 1.75, ci_build_suite, macos-latest)
    • check-success=e2e (3.14, 1.75, ci_build_suite, ubuntu-latest)
    • check-success=e2e (3.14, 1.75, ci_config_suite, macos-latest)
    • check-success=e2e (3.14, 1.75, ci_config_suite, ubuntu-latest)
    • check-success=e2e (3.14, 1.75, ci_specialized_suite, macos-latest)
    • check-success=e2e (3.14, 1.75, ci_specialized_suite, ubuntu-latest)
    • check-success=e2e (3.14, 1.75, ci_workflow_suite, macos-latest)
    • check-success=e2e (3.14, 1.75, ci_workflow_suite, ubuntu-latest)
    • check-success=pkglint
    • check-success=pre-commit
    • check-success=readthedocs
    • check-success=unit (3.12, 1.75, ubuntu-latest)
    • check-success=unit (3.13, 1.75, macos-latest)
    • check-success=unit (3.13, 1.75, ubuntu-latest)
    • check-success=unit (3.14, 1.75, macos-latest)
    • check-success=unit (3.14, 1.75, ubuntu-latest)
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Auto-update approved PRs that are behind (update)

  • #approved-reviews-by>=1
  • #commits-behind > 0 [📌 update requirement]
  • #commits-behind>0
  • -closed [📌 update requirement]
  • -conflict
  • -conflict [📌 update requirement]
  • -draft
  • author!=dependabot[bot]
  • base=main
  • queue-position = -1 [📌 update requirement]

Rule: Ping author on conflicts (comment)

  • conflict
  • -closed

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com