feat: create workspace from new branch button in Branches sub-tab#1408
Open
yeikel16 wants to merge 1 commit intostablyai:mainfrom
Open
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
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
Adds a + button to the right of the branch search input in the Branches sub-tab of the "Create from…"
workspace composer. Clicking it opens a small dialog where the user can type a new branch name and
immediately create a workspace rooted at that branch — without leaving the sub-tab or switching to the
Quick composer.
Previously, users who typed a branch name that didn't exist yet had no direct path forward from the
Branches sub-tab. They had to manually switch to the Quick tab and retype the name.
Changes:
Branches sub-tab, disabled while a launch is in progress); adds a Dialog with a branch-name input that
calls launchFromBranch on confirm.
can pass the user-typed branch name directly instead of falling through to the creature-name generator.
Screenshots
Testing
not possible without a separate setup. The core name-resolution logic (getWorkspaceSeedName with
explicitName) is already covered by src/renderer/src/lib/new-workspace.test.ts. The launchFromBranch path
exercised by this feature is the same one used by existing branch-row selections (no new code paths in
the main process).
Resolve #1400