Skip to content

merge queue: checking main (7f0793f) and #12230 together #12243

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mergify wants to merge 2 commits into from
Closed

merge queue: checking main (7f0793f) and #12230 together #12243

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6a5cbfd
docs(merge-queue): partition_rules are removed, not deprecated
jd Jul 27, 2026
4d4c3ae
Merge of #12230
mergify[bot] Jul 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 12 additions & 5 deletions src/content/docs/merge-queue/migrate-partitions-to-scopes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,16 @@
---
title: Migrate from Partition Rules to Scopes
description: Step-by-step guide to replace the deprecated partition_rules with scopes and scope-aware CI.
description: Step-by-step guide to replace partition_rules, which Mergify no longer supports, with scopes and scope-aware CI.
---

`partition_rules` are deprecated and will be removed in a future release. This
guide walks you through replacing them with **scopes**, a more powerful system
that integrates with your CI and unlocks smarter batching, parallel merge
queues, and monorepo-aware workflows.
`partition_rules` are no longer part of the Mergify configuration. A file that
still declares them is not rejected, but Mergify ignores the section: the queue
stops splitting into partition lanes, and Mergify opens an automatic migration
pull request that strips it out.

This guide walks you through replacing partitions with **scopes**, a system that
integrates with your CI and unlocks smarter batching, parallel merge queues, and
monorepo-aware workflows.

## Why Migrate?

Expand Down Expand Up @@ -176,6 +180,9 @@ Delete the entire `partition_rules` section from `.mergify.yml`. If you
referenced `partition-name` or `current-partition-name` in your
`pull_request_rules` conditions, remove those conditions. They no longer apply.

If Mergify has already opened an automatic migration pull request for your
repository, merging it does this step for you.

### 4. Enable parallel mode

With partitions, independent lanes ran in parallel by design. With scopes, you
Expand Down
3 changes: 2 additions & 1 deletion src/content/docs/merge-queue/queue-modes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -487,7 +487,8 @@ aren't available depending on the mode:
independent, so a passing batch can't vouch for any other. It works in serial and parallel modes,
where a passing batch vouches for the earlier changes it was tested on top of.

- **`partition_rules` are not supported.** Partitions rely on serial ordering; use scopes instead.
Independently of the mode, `partition_rules` are no longer part of the configuration: use scopes
instead. See [Migrate from Partition Rules to Scopes](/merge-queue/migrate-partitions-to-scopes).

## Next Steps

Expand Down