hive-forge: default pr create --push remote to origin
Fresh clones only have origin, not forge. The --remote override already covers anyone using a different name. Closes #4538
This commit is contained in:
parent
2e97ab9dc5
commit
18f0199566
2 changed files with 4 additions and 4 deletions
|
|
@ -534,7 +534,7 @@ Create a pull request
|
|||
* `--body-file <BODY_FILE>` — Read body from a file. `-` means stdin
|
||||
* `--draft` — Open as draft. Ignored in `--agit` mode
|
||||
* `--push` — Push the local `--head` branch to `--remote` before creating the PR
|
||||
* `--remote <REMOTE>` — Remote to push to (default: `forge`, or `origin` in `--agit` mode)
|
||||
* `--remote <REMOTE>` — Remote to push to (default: `origin`)
|
||||
* `--agit` — Open the PR via Forgejo's `AGit` flow instead of pushing a branch — works for read-only collaborators. Run from inside a cloned repo
|
||||
* `--topic <TOPIC>` — `AGit` topic — groups repeated pushes into one PR (re-run with the same topic to update it). Defaults to the branch name. Only meaningful with `--agit`
|
||||
* `--label <LABELS>` — Label name to attach, repeatable (for example `--label area/ops --label type/bug`). Same spelling `labels add` accepts — an unresolved name errors out rather than silently attaching fewer labels than asked for. In `--agit` mode `pr create` applies this as a follow-up call once it learns the PR number (the `AGit` push itself has no label field), so it silently skips them (not a label-resolution error) if it couldn't parse the PR URL back out of the push output — same fallback as the deferred multi-line body
|
||||
|
|
|
|||
Loading…
Reference in a new issue