fix(cmd): keep pr ci out of the CLI surface#239
Merged
barrettruth merged 1 commit intomainfrom Apr 13, 2026
Merged
Conversation
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
:Forgeis meant to stay action-oriented, but:Forge pr cistill exposed a list-based picker workflow through the Ex command surface. That kept one interactive picker path wired into the CLI even after direct create flows were made non-interactive.Solution
Remove
pr cifrom the:Forgecommand grammar and completion surface. Interactive CI and per-PR checks remain available through the picker UI, including nested checks opened from the PR picker, but the Ex command surface now stays limited to semantic direct actions.