Skip to content

docs(workflow): fix action reference accuracy and style drift - #12206

Merged
mergify[bot] merged 1 commit into
mainfrom
devs/jd/jd/mrgfy-8212-docs-health-non-deterministic-audit-loop-style-accuracy/fix-action-ref-accuracy-style-drift--2b9d507d
Jul 27, 2026
Merged

docs(workflow): fix action reference accuracy and style drift#12206
mergify[bot] merged 1 commit into
mainfrom
devs/jd/jd/mrgfy-8212-docs-health-non-deterministic-audit-loop-style-accuracy/fix-action-ref-accuracy-style-drift--2b9d507d

Conversation

@jd

@jd jd commented Jul 26, 2026

Copy link
Copy Markdown
Member

First docs-health audit pass over the action reference pages. Accuracy fixes
verified against the config JSON schema and the engine source:

  • queue: reference auto_merge_conditions instead of the deprecated
    auto_merge
  • comment: fix the copy-pasted rule name in the conflict example (was
    "comment when a pull request is merged" on a conflict condition)
  • delete_head_branch and rebase: convert dated deprecation notices to
    dateless markers per the repo rule (both dates had passed; the
    delete_head_branch date also disagreed with the engine's actual deadline,
    flagged separately in the audit report)
  • post_check: drop the unused Button import; name Merge Protections as the
    feature in prose

Every documented option, default, and enum on all 21 action pages was
cross-checked against the schema; the rest were accurate.

Plus a conservative style pass per the proofread rubrics: banned words,
promotional filler sentences, em dashes, and a dozen grammar fixes across
15 pages.

Part of the first manual docs-health audit (MRGFY-8212).

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

Depends-On: #12205

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections July 26, 2026 08:14 Failure
@jd

jd commented Jul 26, 2026

Copy link
Copy Markdown
Member Author

This pull request is part of a Mergify stack:

# Pull Request Link
1 docs(configuration): fix reference accuracy and style drift #12205
2 docs(workflow): fix action reference accuracy and style drift #12206 👈
3 docs(merge-queue): fix accuracy drift and style across the section #12207
4 docs(commands,merge-protections,migrate): fix broken examples and style #12208
5 docs(ci-insights,test-insights,monorepo-ci): fix wrong commands and claims #12209
6 docs(stacks,integrations,cli,api): fix CLI and integration inaccuracies #12210
7 docs(enterprise,misc): fix inverted Redis TLS instructions and style #12211

@mergify

mergify Bot commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 7 merge protections satisfied — ready to merge.

Show 7 satisfied protections

🟢 ⛓️ Depends-On Requirements

Requirement based on the presence of Depends-On in the body of the pull request

🟢 🤖 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:
      • check-success=Cloudflare Pages
      • -head-repo-full-name~=^Mergifyio/

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • 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 July 26, 2026 08:16
@jd
jd marked this pull request as ready for review July 26, 2026 08:19
First docs-health audit pass over the action reference pages. Accuracy fixes
verified against the config JSON schema and the engine source:

- queue: reference `auto_merge_conditions` instead of the deprecated
  `auto_merge`
- comment: fix the copy-pasted rule name in the conflict example (was
  "comment when a pull request is merged" on a `conflict` condition)
- delete_head_branch and rebase: convert dated deprecation notices to
  dateless markers per the repo rule (both dates had passed; the
  delete_head_branch date also disagreed with the engine's actual deadline,
  flagged separately in the audit report)
- post_check: drop the unused Button import; name Merge Protections as the
  feature in prose

Every documented option, default, and enum on all 21 action pages was
cross-checked against the schema; the rest were accurate.

Plus a conservative style pass per the proofread rubrics: banned words,
promotional filler sentences, em dashes, and a dozen grammar fixes across
15 pages.

Part of the first manual docs-health audit (MRGFY-8212).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Change-Id: I2b9d507db7a3e2ab566d70b0b15a28031f427962
@jd
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 da17747 to 151c2d1 Compare July 26, 2026 08:23
@jd
jd force-pushed the devs/jd/jd/mrgfy-8212-docs-health-non-deterministic-audit-loop-style-accuracy/fix-ref-accuracy-style-drift--a5524167 branch from 23a05f1 to 3b32271 Compare July 26, 2026 08:23
@jd

jd commented Jul 26, 2026

Copy link
Copy Markdown
Member Author

Revision history

# Type Changes Reason Date
1 initial da17747 2026-07-26 08:22 UTC
2 rebase da17747 → 151c2d1 (rebase only) 2026-07-26 08:22 UTC

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections July 26, 2026 08:23 Failure
JulianMaurin
JulianMaurin previously approved these changes Jul 27, 2026
@mergify
mergify Bot requested a review from a team July 27, 2026 07:29
Base automatically changed from devs/jd/jd/mrgfy-8212-docs-health-non-deterministic-audit-loop-style-accuracy/fix-ref-accuracy-style-drift--a5524167 to main July 27, 2026 07:32
@mergify
mergify Bot dismissed JulianMaurin’s stale review July 27, 2026 07:32

The base branch was changed.

@mergify
mergify Bot 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 151c2d1 to 8207564 Compare July 27, 2026 07:32
@mergify
mergify Bot deployed to Mergify Merge Protections July 27, 2026 07:32 Active
@mergify

mergify Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 minutes 24 seconds in the queue, including 2 minutes 1 second running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Jul 27, 2026
@mergify
mergify Bot merged commit c67b89a into main Jul 27, 2026
9 checks passed
@mergify
mergify Bot deleted the devs/jd/jd/mrgfy-8212-docs-health-non-deterministic-audit-loop-style-accuracy/fix-action-ref-accuracy-style-drift--2b9d507d branch July 27, 2026 07:37
@mergify mergify Bot removed the queued label Jul 27, 2026
mergify Bot pushed a commit that referenced this pull request Jul 27, 2026
…12207)

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>

Depends-On: #12206
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.

3 participants