From 23850e633bff66982e3950e4fcdee1f0750ad65c Mon Sep 17 00:00:00 2001 From: atlas Date: Fri, 11 Sep 2026 03:35:18 +0200 Subject: [PATCH] docs: regenerate forge-cli.md for pr status's positional MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `docs/tools/forge-cli.md` is generated from the clap tree, so changing an argument or its doc comment changes that file too. The freshness check in `checks.hive-forge-docs` is what says so, and it is what failed here — after 8m44s, on a PR that was already approved. Regenerated, no hand edits. Two hunks, both the `pr status` section, and `nix fmt` leaves the result byte-identical so the formatter and the generator are not fighting over it. Part of #4182. --- docs/tools/forge-cli.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/tools/forge-cli.md b/docs/tools/forge-cli.md index 857817ef..5747f86a 100644 --- a/docs/tools/forge-cli.md +++ b/docs/tools/forge-cli.md @@ -548,12 +548,16 @@ Create a pull request PR health view: mergeable / CI / reviews -**Usage:** `hive-forge pr status [OPTIONS]` +**Usage:** `hive-forge pr status [OPTIONS] [NUMBER]` + +###### **Arguments:** + +* `` — PR number — full health view (mergeable, CI, reviews, last comment). Mutually exclusive with `--sha` ###### **Options:** -* `--pr ` — PR number — full health view (mergeable, CI, reviews, last comment). Mutually exclusive with `--sha` -* `--sha ` — Explicit commit sha (or ref) — CI-only fast path. Mutually exclusive with `--pr` +* `--pr ` — Same as passing the number positionally. Kept because this verb accepted only this spelling before the positional existed +* `--sha ` — Explicit commit sha (or ref) — CI-only fast path. Mutually exclusive with a PR number