cmd: make :Forge pr create strictly create-only #392

New issue

Closed

opened 2026-04-25 16:20:53 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-04-25 16:20:53 +00:00

Part of #389.
Depends on #391.
Suggested order: 3.

Problem

:Forge pr create currently overloads creation and branch->existing-PR lookup. That makes the command surprising and hides the distinction between "create a new PR" and "act on the current branch PR".

Proposed solution

Make :Forge pr create strictly creation-oriented. If a matching open PR already exists for the resolved head context, stop and report a clear message directing the user to :Forge pr or :Forge review instead of silently switching into edit.

Scope

remove the existing-PR redirect from the create flow
keep the message precise and actionable
update create-flow specs

Acceptance criteria

:Forge pr create never opens the current PR edit path implicitly
when a matching PR already exists, the command exits cleanly and tells the user which current-PR command to use instead
existing pure create flows still work with repo= / head= / base=

Out of scope

adding new Lua APIs
final documentation cleanup beyond the command behavior touched here

Part of #389. Depends on #391. Suggested order: 3. ## Problem `:Forge pr create` currently overloads creation and branch->existing-PR lookup. That makes the command surprising and hides the distinction between "create a new PR" and "act on the current branch PR". ## Proposed solution Make `:Forge pr create` strictly creation-oriented. If a matching open PR already exists for the resolved head context, stop and report a clear message directing the user to `:Forge pr` or `:Forge review` instead of silently switching into edit. ## Scope - remove the existing-PR redirect from the create flow - keep the message precise and actionable - update create-flow specs ## Acceptance criteria - `:Forge pr create` never opens the current PR edit path implicitly - when a matching PR already exists, the command exits cleanly and tells the user which current-PR command to use instead - existing pure create flows still work with `repo=` / `head=` / `base=` ## Out of scope - adding new Lua APIs - final documentation cleanup beyond the command behavior touched here