docs(ci): describe the queue as configured, not as pending - #11367
Open
andres-pcg wants to merge 1 commit into
Open
docs(ci): describe the queue as configured, not as pending#11367andres-pcg wants to merge 1 commit into
andres-pcg wants to merge 1 commit into
Conversation
|
Warning No auditable source files found in this PR's diff. |
The hold section still said neither check was required and pointed at a list of activation steps. Both are required now, and every step in that list has been applied, so the section becomes a description of the configuration — including why the check response timeout is raised from its default of 60 minutes to 180: unit tests take up to 69, so at the default the queue would give up waiting and drop every entry that touches Rust while its checks were still running. The release checklist also named the Merge Freeze action "Unfreeze 1 pull request"; the dashboard calls it "Unblock 1 pull request". Its freeze method is confirmed as the one that offers it, so the caveat about checking first is replaced by the cost that does apply: a status write per open pull request, at about a second each.
andres-pcg
force-pushed
the
docs/merge-freeze-unblock
branch
from
September 1, 2026 01:15
c72034b to
f05e99a
Compare
conradoplg
approved these changes
Sep 1, 2026
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
2 participants
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.
Motivation
The queue documentation merged with #11324 described the state before activation. The cutover has since happened:
merge-policyandmergefreezeare required status checks, themerge_queuerule is in the ruleset, Mergify's bypass actor is gone and the app is uninstalled. The book still told readers that neither hold was enforced, and pointed at a list of steps that have all been applied.Solution
Activating the queuebecomesQueue configuration: what the ruleset requires and why, keeping the reason the check response timeout is raised from its default of 60 minutes to 180. Unit tests take up to 69, so at the default the queue would stop waiting and drop every entry that touches Rust as assumed-failed while its checks were still running..github/workflows/README.md.Tests
Documentation only. Verified against the live configuration: six required checks each pinned to its producing app,
merge_method: MERGE, build concurrency 5,ALLGREEN, 1–1 entries, 2-minute wait, 180-minute timeout, and no Mergify bypass actor. Checked that no reference to the old#activating-the-queueanchor remains.AI Disclosure
PR Checklist
type(scope): description