docs(merge-queue): stops claiming batches require the up-to-date setting to be off; batch grouping… - #13034
Merged
Conversation
…ing to be off; batch grouping…
Contributor
Merge Protections🟢 All 5 merge protections satisfied — ready to merge. Show 5 satisfied protections🟢 👀 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
approved these changes
Sep 28, 2026
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
|
49 tasks
This branch was successfully deployed
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 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-forwardqueue, and in-placechecks. 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 anoption 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: rebaseanswers a linear-history requirement and does nothingabout 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.