docs(agent): corrects the merge queue check-run name and the stale tmp- branch claim - #12609
Merged
mergify[bot] merged 1 commit intoSep 1, 2026
Conversation
Contributor
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. |
jd
reviewed
Aug 31, 2026
mergify-ci-bot
force-pushed
the
docs-agent/health-audit-merge-queue-1
branch
from
August 31, 2026 10:28
35a8438 to
5d1ceb9
Compare
Contributor
Author
|
AlexandreGaubert
approved these changes
Aug 31, 2026
remyduthu
approved these changes
Sep 1, 2026
Contributor
Merge Queue Status
This pull request spent 4 minutes 55 seconds in the queue, including 3 minutes 47 seconds running CI. Required conditions to merge
|
63 tasks
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.
The merge queue lifecycle page told readers to look for a "Mergify — Queued" status in
the Checks tab of a queued pull request. No such status exists. There is a single
consolidated check run named "Mergify Merge Queue", and it is the check's title that
reports where the pull request stands: "In merge queue" while it waits its turn,
"Running merge queue checks" once its batch is under test. The paragraph now names the
check run and quotes those two titles.
The queue branch cleanup section described the
tmp-variant as a temporary branchMergify creates during setup. It is not created at all any more: the queue pushes
straight to the final branch name, and the prefix survives only in the cleanup scan,
which still matches it so a branch left behind by an older version is removed. The page
now says that, without the example that made the older name look current. The optional
tmp-stays in the matching rule, because a branch you name that way yourself is stilleligible for deletion.
The lifecycle summary also stated flatly that merges happen in queue order, one batch at
a time. That is serial mode, which is the default but not the only one: in parallel and
isolated modes, batches with no dependency between them merge as soon as their own
checks pass, which is the whole point of those modes. The sentence is now scoped to
serial and the other two are named, so it no longer contradicts the queue modes page.
Finally, the merge strategies page headed its
mergesection "Merge (Default)".merge_methodhas no default in the configuration schema; when it is unset Mergify usesthe first method the repository authorizes, which the section body already explained.
The heading now just reads "Merge".
Open question: the Checks-tab screenshot on the lifecycle page still pictures the older
per-rule check runs and needs reshooting against the consolidated check.