fix(cmd): keep direct Forge actions picker-free#238
Merged
barrettruth merged 1 commit intomainfrom Apr 13, 2026
Merged
Conversation
barrettruth
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Some direct
:Forgecommand paths still depended on the picker layer.:Forge pr createand:Forge issue createcould prompt for templates, and:Forge pr ciexposed a list-based picker workflow through the Ex command surface. That conflicted with the intended contract that:Forgestays action-oriented while interactive list workflows live behind the picker UI.Solution
Keep direct create flows non-interactive and remove the remaining picker-backed PR CI verb from the command grammar. PR and issue creation now fall back to normal compose behavior instead of prompting for template selection, and
:Forge pr ciis no longer a valid Ex command. Interactive CI and per-PR checks remain available through the picker surface and nested picker actions.