docs(merge-queue): show classic branch protection path for exclusive mode#12190
Open
jd wants to merge 1 commit into
Open
Conversation
…mode Wire the two orphaned screenshots in deploy/ (bp-settings.png, bp-rule.png) into the "Approach 2: Exclusive Mode" section of merge-queue/deploy.mdx. The exclusive-mode steps previously said "follow the on-screen instructions" and "click the verification button" without showing the GitHub UI. These two screenshots document the classic branch-protection way to enforce exclusive mode: restrict who can push to the protected branch to the Mergify app only. They are added as a clearly-labeled "Enforcing Exclusive Mode with Classic Branch Protection" alternative, NOT mixed into the recommended ruleset + bypass-list flow (which the dashboard actively recommends and which the fresh deploy/dashboard.png already illustrates). Classic branch protection is a supported, already-documented path elsewhere in these docs (batches.mdx, merge-strategies.mdx). Judgment call for review: the orphaned bp-* assets document classic branch protection while the current section documents the ruleset flow. If the intent is for deploy.mdx to stay ruleset-only, drop this commit and the bp-* images become deletion candidates. Part 3 (Merge Queue) of the docs screenshot refresh. The other Part 3 items resolved without a diff: all 7 freshness-verify pages (batches, lifecycle, merge-strategies, monitoring, pause, setup, deploy) show the current dashboard / GitHub UI -> OK, no re-capture; and the github-rulesets.mdx bypass-actor capture was declined (GitHub's own UI, already a clear textual click-through). Proofreading: the mandated 4-agent proofread pipeline (style, technical, structure, consistency) was run this session and passed clean; one precision fix was applied to the closing sentence. Refs: MRGFY-8060 Change-Id: I5c33dfa7d7a144b27cea064f0bf4ec9f64148719
Contributor
Merge Protections🔴 2 of 6 protections blocking · waiting on 👀 reviews
🔴 👀 Review RequirementsWaiting for
This rule is failing.
🔴 🔎 ReviewsWaiting for
This rule is failing.
Show 4 satisfied protections🟢 🤖 Continuous Integration
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 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
This PR updates the Merge Queue deployment documentation to include a clearly separated “classic branch protection” path for enforcing Exclusive Mode, wiring in two previously orphaned screenshots so readers can follow the GitHub UI steps.
Changes:
- Import and use two GitHub branch protection screenshots (
bp-settings.png,bp-rule.png) inmerge-queue/deploy.mdx. - Add a new subsection describing how to enforce Exclusive Mode using classic branch protection (restrict push access to the Mergify app).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
mergify
Bot
added
review threads unresolved
and removed
review threads unresolved
labels
jd
marked this pull request as ready for review
July 25, 2026 15:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wire the two orphaned screenshots in deploy/ (bp-settings.png, bp-rule.png)
into the "Approach 2: Exclusive Mode" section of merge-queue/deploy.mdx.
The exclusive-mode steps previously said "follow the on-screen instructions"
and "click the verification button" without showing the GitHub UI. These two
screenshots document the classic branch-protection way to enforce exclusive
mode: restrict who can push to the protected branch to the Mergify app only.
They are added as a clearly-labeled "Enforcing Exclusive Mode with Classic
Branch Protection" alternative, NOT mixed into the recommended ruleset +
bypass-list flow (which the dashboard actively recommends and which the fresh
deploy/dashboard.png already illustrates). Classic branch protection is a
supported, already-documented path elsewhere in these docs (batches.mdx,
merge-strategies.mdx).
Judgment call for review: the orphaned bp-* assets document classic branch
protection while the current section documents the ruleset flow. If the intent
is for deploy.mdx to stay ruleset-only, drop this commit and the bp-* images
become deletion candidates.
Part 3 (Merge Queue) of the docs screenshot refresh. The other Part 3 items
resolved without a diff: all 7 freshness-verify pages (batches, lifecycle,
merge-strategies, monitoring, pause, setup, deploy) show the current dashboard
/ GitHub UI -> OK, no re-capture; and the github-rulesets.mdx bypass-actor
capture was declined (GitHub's own UI, already a clear textual click-through).
Proofreading: the mandated 4-agent proofread pipeline (style, technical,
structure, consistency) was run this session and passed clean; one precision
fix was applied to the closing sentence.
Refs: MRGFY-8060