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
1 changed files with 73 additions and 73 deletions
|
|
@ -91,7 +91,7 @@ pub fn run(client: &Client, args: Args) -> Result<()> {
|
|||
}
|
||||
|
||||
/// The repo's whole label set, for name → id resolution. `pub(crate)` so
|
||||
/// other verbs (`issue-create`, `pr-create`, `list`) can resolve a label
|
||||
/// other verbs (`issue create`, `pr create`, `list`) can resolve a label
|
||||
/// name without duplicating the lookup.
|
||||
///
|
||||
/// Paginated, where this used to ask for one page of 100 — **a page size
|
||||
|
|
@ -127,7 +127,7 @@ pub(crate) fn repo_labels(client: &Client) -> Result<Vec<Label>> {
|
|||
/// Resolve label names to ids, hard-erroring if any name doesn't match an
|
||||
/// existing repo label. A typo used to silently produce fewer labels than
|
||||
/// intended with no signal — not even a nonzero exit code — so callers
|
||||
/// (`labels add`, `issue-create --label`, `pr-create --label`) had no way
|
||||
/// (`labels add`, `issue create --label`, `pr create --label`) had no way
|
||||
/// to notice without manually diffing what they asked for against what
|
||||
/// landed. The error lists both the exact names that didn't resolve and
|
||||
/// every label actually available on the repo, so it's fixable from the
|
||||
|
|
|
|||
Loading…
Reference in a new issue