docs, prompts, hive-forge: stop handing readers the renamed verbs
docs/tools/forge.md already listed the nine renamed verbs as removed, then used them ~30 more times in pasteable blocks. Sweeps every occurrence a reader would type, including three runtime messages that told the user to run a verb the same binary rejects. The renamed-verb list itself keeps the old names; it is what documents them. Refs #4155
This commit is contained in:
parent
d2175c84b3
commit
55f01942a2
23 changed files with 73 additions and 73 deletions
|
|
@ -6,7 +6,7 @@
|
|||
//! the only path is the web UI's download route,
|
||||
//! `<base>/<owner>/<repo>/actions/runs/<run-id>/artifacts/<name>`. That
|
||||
//! route is keyed by the run's GLOBAL id, **not** the per-repo run number
|
||||
//! the UI shows in run-page URLs (`/actions/runs/51`) and that `pr-status`
|
||||
//! the UI shows in run-page URLs (`/actions/runs/51`) and that `pr status`
|
||||
//! surfaces as a CI context's `target_url`. The REST artifacts *list*
|
||||
//! route, confusingly, keys off the run number instead — so the two can't
|
||||
//! be chained directly. We therefore translate the caller's run number
|
||||
|
|
@ -32,7 +32,7 @@ pub struct Args {
|
|||
/// Artifact name, as shown on the run page (for example `pr1ma-paper-pdf`).
|
||||
name: String,
|
||||
/// Workflow run number — the `runs/<n>` in the run-page URL, which
|
||||
/// `pr-status` surfaces as a CI context's `target_url`. (This is the
|
||||
/// `pr status` surfaces as a CI context's `target_url`. (This is the
|
||||
/// per-repo run number, not the global run id; the verb translates.)
|
||||
#[arg(long)]
|
||||
run: u64,
|
||||
|
|
|
|||
Loading…
Reference in a new issue