docs(merge-queue): fix accuracy drift and style across the section#12207
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
This was referenced Jul 26, 2026
Contributor
Merge Protections🔴 3 of 7 protections blocking · waiting on 👀 reviews and ⛓️ dependency
🔴 ⛓️ Depends-On RequirementsWaiting for
This rule is failing.Requirement based on the presence of
🔴 👀 Review RequirementsWaiting for
This rule is failing.
🔴 🔎 ReviewsWaiting for
This rule is failing.
Show 4 satisfied protections🟢 🤖 Continuous Integration
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
marked this pull request as ready for review
July 26, 2026 08:20
First docs-health audit pass over all merge-queue pages. Accuracy fixes
verified against the config JSON schema, the CLI schema, and the engine:
- github-rulesets: add the missing `none` value of
`branch_protection_injection_mode` (schema enum queue|merge|none)
- scopes: remove the wrong "set `merge_queue_scope` to `null` to
disable" claim (schema types it non-nullable)
- batches: "split into two by default" was stale; the engine splits a
failed batch into max(2, max_parallel_checks) parts
- queue-modes: isolated-mode batching without scopes fills by
changed-directory similarity, not pure arrival order; fast-forward
restriction list was missing `squash` as an allowed method
- lifecycle: reference `auto_merge_conditions` instead of the deprecated
`auto_merge`
- pause: `--reason` is required, not optional (CLI schema); fix the broken
freeze anchor to /merge-protections/freeze
- monitoring: match the dashboard UI text ("Past 3 months")
- rules and merge-strategies: convert expired dated deprecation notices
(autoqueue, fork-rebase) to dateless markers per the repo rule
Plus a conservative style pass per the proofread rubrics: banned words,
~50 prose em dashes, throat-clearing intros, promotional filler, and
grammar fixes. Frontmatter descriptions with banned words or em dashes
were also cleaned (quoted where a colon required it).
Part of the first manual docs-health audit (MRGFY-8212).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Change-Id: Id3c23f7e14e230717281da16da2ca8f2e491ab5b
jd
force-pushed
the
devs/jd/jd/mrgfy-8212-docs-health-non-deterministic-audit-loop-style-accuracy/fix-accuracy-drift-style-across-section--d3c23f7e
branch
from
July 26, 2026 08:23
c045428 to
b1bd5e4
Compare
jd
force-pushed
the
devs/jd/jd/mrgfy-8212-docs-health-non-deterministic-audit-loop-style-accuracy/fix-action-ref-accuracy-style-drift--2b9d507d
branch
from
July 26, 2026 08:23
da17747 to
151c2d1
Compare
Member
Author
Revision history
|
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
1 participant
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.
First docs-health audit pass over all merge-queue pages. Accuracy fixes
verified against the config JSON schema, the CLI schema, and the engine:
nonevalue ofbranch_protection_injection_mode(schema enum queue|merge|none)merge_queue_scopetonulltodisable" claim (schema types it non-nullable)
failed batch into max(2, max_parallel_checks) parts
changed-directory similarity, not pure arrival order; fast-forward
restriction list was missing
squashas an allowed methodauto_merge_conditionsinstead of the deprecatedauto_merge--reasonis required, not optional (CLI schema); fix the brokenfreeze anchor to /merge-protections/freeze
(autoqueue, fork-rebase) to dateless markers per the repo rule
Plus a conservative style pass per the proofread rubrics: banned words,
~50 prose em dashes, throat-clearing intros, promotional filler, and
grammar fixes. Frontmatter descriptions with banned words or em dashes
were also cleaned (quoted where a colon required it).
Part of the first manual docs-health audit (MRGFY-8212).
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Depends-On: #12206