fix(create-web): report web flow outcomes#192
Merged
barrettruth merged 1 commit intomainfrom Apr 12, 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
The web create paths ran their browser-opening command without checking whether it succeeded, so Forge could fail silently. That made
:Forge issue create weband:Forge pr create webfeel unreliable, and URL-based providers like Codeberg also bypassed Forge-level reporting.Solution
Route PR and issue web-create flows through shared outcome handling in
forge.init. Command-backed flows now log a Forge-level success message on exit code 0 and surface stderr/stdout on failure. URL-based flows now report browser open failures too, and Codeberg PR creation now returns its compare URL so it goes through the same reporting path.