hive-forge: add dependency verb for issue/pr blocking relationships
This commit is contained in:
parent
32643dae36
commit
6a95aceedb
6 changed files with 121 additions and 11 deletions
|
|
@ -21,7 +21,7 @@ under `issue` and `pr` parent commands — `hive-forge pr close 42`,
|
|||
refuses an issue number, which the old generic `close` couldn't). Run
|
||||
`hive-forge pr --help` / `hive-forge issue --help` for the full subcommand
|
||||
list (show/create/edit/status/merge/reviews/commits/diff/view/comment/
|
||||
comments/close/reopen/labels/assign/timeline as applicable).
|
||||
comments/close/reopen/labels/assign/dependency/timeline as applicable).
|
||||
|
||||
The flat forms below (`close 42`, `pr-create …`, `pr-status …`, …) still work
|
||||
as **hidden back-compat aliases** during the transition and are dropped from
|
||||
|
|
@ -49,6 +49,10 @@ hive-forge comment-edit 18042 --body "..." # edit a comment
|
|||
hive-forge assign 42 damocles
|
||||
hive-forge close 42
|
||||
hive-forge labels 42 add feature
|
||||
hive-forge issue dependency 42 # list #42's dependencies (issues it's blocked by)
|
||||
hive-forge issue dependency 42 add 40 41 # #42 is now blocked by #40 and #41
|
||||
hive-forge issue dependency 42 remove 40 # drop the #40 dependency link
|
||||
hive-forge pr dependency 55 add 42 # same verb, PR-scoped (Forgejo shares the issue/PR index)
|
||||
hive-forge issue-create --title "..." --body "..."
|
||||
hive-forge issue-create --title "..." --body "..." --label area/ops --label type/bug # repeatable
|
||||
hive-forge issue-edit 42 --title "new title"
|
||||
|
|
@ -273,6 +277,13 @@ to discover valid label names before triaging or to audit the label set.
|
|||
<name>` (directly). `--workflow <file>` picks the workflow file for
|
||||
`--pr` / `--branch` (default `ci.yml`). Dispatch re-runs the whole
|
||||
workflow — there is no single-job variant.
|
||||
- `issue dependency <n> add <dep...>` / `pr dependency <n> add <dep...>`
|
||||
set "blocked by" links via Forgejo's dependency feature — the
|
||||
operator's preferred way to track blocking relationships over labels
|
||||
(labels can go stale; dependencies are structured and show in the
|
||||
forge UI's dependency panel). Same-repo only, matching the web UI (no
|
||||
cross-repo dependency support). `list` (the default action) and `add`/
|
||||
`remove` all print the resulting dependency list as JSON.
|
||||
- Do NOT use raw `curl` for forge access -- the CLI handles auth,
|
||||
error checking, and output formatting.
|
||||
- `issue-create --label <name>` / `pr-create --label <name>` are
|
||||
|
|
|
|||
Loading…
Reference in a new issue