docs(merge-queue): partition_rules are removed, not deprecated - #12230
Conversation
|
This pull request is part of a Mergify stack:
|
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
There was a problem hiding this comment.
Pull request overview
Updates merge-queue documentation to reflect that partition_rules have already been removed (not merely deprecated), and explains current behavior/migration guidance so readers aren’t misled by outdated deprecation language.
Changes:
- Updates Queue modes docs to state
partition_rulesare no longer supported in any mode and points readers to the migration guide. - Updates the migration guide intro to describe the current behavior when
partition_rulesare still present (ignored + migration PR). - Adds a note that merging the auto-opened migration PR can perform the removal step for you.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/content/docs/merge-queue/queue-modes.mdx | Replaces the mode-specific limitation blurb with a mode-independent note + link to migration guide. |
| src/content/docs/merge-queue/migrate-partitions-to-scopes.mdx | Rewords the guide to reflect removal (not deprecation) and clarifies the migration PR behavior. |
Comments suppressed due to low confidence (1)
src/content/docs/merge-queue/migrate-partitions-to-scopes.mdx:184
- For consistency with other pages that mention Mergify-created config updates, prefer “automatic migration pull request” over “configuration migration pull request”.
If Mergify has already opened a configuration migration pull request for your
repository, merging it does this step for you.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The migration guide still told readers `partition_rules` were "deprecated and will be removed in a future release". They are already gone: the key is absent from `public/mergify-configuration-schema.json` and from the engine's configuration model, having disappeared between the 2026-06-02 and 2026-06-12 schema syncs with no changelog entry. Describe what actually happens now. The configuration model allows extra keys, so a file still declaring `partition_rules` is not rejected: Mergify ignores the section, the queue stops splitting into partition lanes, and the extra-keys transformer opens a configuration migration pull request that strips it out. Step 3 notes that merging that pull request does the work for you. In queue-modes, `partition_rules` was listed as an isolated-mode limitation. It is not mode-specific any more, so it moves out of the limitations list into a sentence pointing at the migration guide. MRGFY-8213 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Change-Id: I5a5aeb9e975a6ec6e7ab15943d930c54023e1a70
214b594 to
6a5cbfd
Compare
Revision history
|
Merge Queue Status
This pull request spent 2 minutes 43 seconds in the queue, including 2 minutes 11 seconds running CI. Required conditions to merge
|
The metrics reference was missing `mergify.queue.skip_intermediate_results.batches_saved`, a count the engine's stats metrics pusher has been submitting alongside the rest of the `mergify.queue.*` family. It is what backs the "Batches Saved" chart on the merge queue Statistics page. Add the table row and a short paragraph explaining what it counts and that it only moves when `skip_intermediate_results` is enabled. The explanation goes in prose rather than the table cell because a metric name that long plus an inline link exceeds the 120-character line limit, and table rows cannot be wrapped. MRGFY-8213 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Depends-On: #12230
The migration guide still told readers
partition_ruleswere "deprecated andwill be removed in a future release". They are already gone: the key is absent
from
public/mergify-configuration-schema.jsonand from the engine'sconfiguration model, having disappeared between the 2026-06-02 and 2026-06-12
schema syncs with no changelog entry.
Describe what actually happens now. The configuration model allows extra keys,
so a file still declaring
partition_rulesis not rejected: Mergify ignores thesection, the queue stops splitting into partition lanes, and the extra-keys
transformer opens a configuration migration pull request that strips it out.
Step 3 notes that merging that pull request does the work for you.
In queue-modes,
partition_ruleswas listed as an isolated-mode limitation. Itis not mode-specific any more, so it moves out of the limitations list into a
sentence pointing at the migration guide.
MRGFY-8213
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com