Skip to content

docs(agent): corrects the merge queue check-run name and the stale tmp- branch claim - #12609

Merged
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-queue-1
Sep 1, 2026
Merged

docs(agent): corrects the merge queue check-run name and the stale tmp- branch claim#12609
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-queue-1

Conversation

@mergify-ci-bot

@mergify-ci-bot mergify-ci-bot commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

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 branch
Mergify 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 still
eligible 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 merge section "Merge (Default)".
merge_method has no default in the configuration schema; when it is unset Mergify uses
the 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.

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections August 30, 2026 22:42 Failure
@mergify

mergify Bot commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success = build
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
    • any of:
      • -head-repo-full-name~=^Mergifyio/
      • check-success=Cloudflare Pages

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • author = renovate[bot]
    • all of:
      • -head ~= ^docs-agent/
      • author = mergify-ci-bot

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

@mergify
mergify Bot requested a review from a team August 30, 2026 22:44
Comment thread src/content/docs/merge-queue/lifecycle.mdx Outdated
@mergify
mergify Bot requested a review from a team August 31, 2026 08:55
@mergify-ci-bot
mergify-ci-bot force-pushed the docs-agent/health-audit-merge-queue-1 branch from 35a8438 to 5d1ceb9 Compare August 31, 2026 10:28
@mergify-ci-bot

Copy link
Copy Markdown
Contributor Author

🤖 I read this review and pushed a new revision.

@mergify
mergify Bot deployed to Mergify Merge Protections August 31, 2026 10:29 Active
@mergify
mergify Bot requested a review from a team August 31, 2026 14:31
@mergify

mergify Bot commented Sep 1, 2026

Copy link
Copy Markdown
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

@mergify
mergify Bot merged commit 08a1937 into Mergifyio:main Sep 1, 2026
9 checks passed
@mergify mergify Bot added queued and removed queued labels Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants