hive-forge: pr edit --base retargets a PR
Forgejo's issue edit endpoint (/issues/<n>) has no base field, so `pr edit` could not retarget a stacked PR once its base merged. `--base <BRANCH>` (non-empty) switches the edit onto PATCH /pulls/<n>, which carries `base` alongside title/body/state/milestone. Without `--base`, `pr edit` is unchanged and still goes through the issue endpoint.
This commit is contained in:
parent
18ed3f5040
commit
9e3a00825b
7 changed files with 348 additions and 27 deletions
|
|
@ -67,6 +67,7 @@ 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"
|
||||
hive-forge pr edit 42 --title "new title" # same edit, PR-kind-validated
|
||||
hive-forge pr edit 42 --base main # retarget a stacked PR onto main
|
||||
hive-forge pr 42 # PR metadata as JSON
|
||||
hive-forge pr create --title "..." --head my-branch --push # also `git push forge my-branch`
|
||||
hive-forge pr create --title "..." --head my-branch --label area/ops # repeatable, same as issue create
|
||||
|
|
|
|||
Loading…
Reference in a new issue