Skip to content

docs(merge-queue): stops claiming batches require the up-to-date setting to be off; batch grouping… - #13034

Merged
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-queue-2--batches-overstates-the-up-to-date-requirement
Sep 28, 2026
Merged

mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-queue-2--batches-overstates-the-up-to-date-requirement

Conversation

@mergify-ci-bot

Copy link
Copy Markdown
Contributor

The batches page stated flatly that batches "require" Require branches to be up
to date before merging
to be disabled. The rulesets page, which this passage
already links to for the details, scopes the conflict to a queue testing on a
temporary batch pull request and lists three resolutions besides disabling the
setting: a bypass actor on the ruleset, a fast-forward queue, and in-place
checks. So a reader who cannot turn that setting off, which is common when it is
set organisation-wide, was being told batches were unavailable to them when other
routes were open.

The passage now states the conflict rather than a requirement and says why GitHub
blocks the merge. It mentions in-place checks with the constraint that decides
whether they are usable at all, batch_size: 1, so nobody reads them as an
option that preserves batching, and it leaves the full list of resolutions to the
page that already enumerates them instead of half-repeating them here.

The linear-history sentence also moved out of the middle of that explanation and
gained the clause it was missing. Sitting directly after the sentence about the
up-to-date setting, it read as a resolution for it, which it is not:
merge_method: rebase answers a linear-history requirement and does nothing
about this setting. Conflating the two is the likeliest way to arrive at a queue
that still will not merge.

Evidence: the engine's protection-conflict detection, which raises this conflict
only when checks do not run in place and skips it for a fast-forward queue, and
the in-place check test, which requires batch_size: 1.

…truncated; the rest is in the run log.

@mergify
mergify Bot deployed to Mergify Merge Protections September 28, 2026 11:09 Active
@mergify

mergify Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 5 merge protections satisfied — ready to merge.

Show 5 satisfied protections

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by >= 1
    • 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 September 28, 2026 11:11
@mergify

mergify Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 3 minutes 26 seconds in the queue, including 2 minutes 50 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Sep 28, 2026
@mergify
mergify Bot merged commit 7f9a9f8 into Mergifyio:main Sep 28, 2026
12 checks passed
@mergify mergify Bot removed the queued label Sep 28, 2026

This branch was successfully deployed

1 active deployment
Mergify Merge Protections — b97994b8 Deployed Sep 28, 2026 by mergify[bot]
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.

2 participants