docs: regenerate forge-cli.md for pr status's positional
`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.
This commit is contained in:
parent
84203a3f9b
commit
23850e633b
1 changed files with 7 additions and 3 deletions
|
|
@ -548,12 +548,16 @@ Create a pull request
|
||||||
|
|
||||||
PR health view: mergeable / CI / reviews
|
PR health view: mergeable / CI / reviews
|
||||||
|
|
||||||
**Usage:** `hive-forge pr status [OPTIONS]`
|
**Usage:** `hive-forge pr status [OPTIONS] [NUMBER]`
|
||||||
|
|
||||||
|
###### **Arguments:**
|
||||||
|
|
||||||
|
* `<NUMBER>` — PR number — full health view (mergeable, CI, reviews, last comment). Mutually exclusive with `--sha`
|
||||||
|
|
||||||
###### **Options:**
|
###### **Options:**
|
||||||
|
|
||||||
* `--pr <PR>` — PR number — full health view (mergeable, CI, reviews, last comment). Mutually exclusive with `--sha`
|
* `--pr <PR>` — Same as passing the number positionally. Kept because this verb accepted only this spelling before the positional existed
|
||||||
* `--sha <SHA>` — Explicit commit sha (or ref) — CI-only fast path. Mutually exclusive with `--pr`
|
* `--sha <SHA>` — Explicit commit sha (or ref) — CI-only fast path. Mutually exclusive with a PR number
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue