Repository navigation
Open issue workspaces automatically after creation - #7
Merged
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.
Summary
Creating an issue workspace previously left the user on the issue list. Both Create actions now open the returned workspace immediately after success, using the owning host for remote projects.
on creation success show success toast + open workspace on the owning host refresh issue coverageEvidence
openWorkspacewas called zero times.After: All 336 tests pass, including wide and compact screens, both Create actions, remote host routing, and no navigation while pending or after failure.
npm run typecheckpasses.runningandPlugin ready.Merge Danger
Door: two-way
Blast Radius: navigation
Successful creation now leaves the issue list and opens the new workspace.