Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix: dismiss new branch dialog immediately for remote branches#57

Merged
wesbillman merged 2 commits intomainfrom
wesb/fix-new-branch-dialog
Feb 12, 2026
Merged

fix: dismiss new branch dialog immediately for remote branches#57
wesbillman merged 2 commits intomainfrom
wesb/fix-new-branch-dialog

Conversation

@wesbillman
Copy link
Collaborator

Summary

  • Split create_remote_branch into two steps: the Tauri command now only creates the DB record and returns immediately, while a new start_workspace command handles Blox provisioning separately
  • The frontend calls onCreated(branch) right away (closing the dialog and showing the branch card in its "Provisioning…" state), then fires startWorkspace in the background
  • Fixed a race condition where Blox briefly reports "stopped" during initial provisioning — when DB status is still Starting, this is now treated as Starting so polling continues

Test plan

  • Open the new branch dialog and create a remote branch
  • Verify the dialog dismisses immediately and the branch card appears in "Provisioning…" state
  • Verify the workspace eventually transitions to Running and the card updates
  • Verify that if Blox briefly reports "stopped" during startup, the card doesn't get stuck — it keeps polling until Running

🤖 Generated with Claude Code

wesbillman and others added 2 commits February 11, 2026 17:10
Split `create_remote_branch` into two steps: the Tauri command now only
creates the DB record and returns immediately, while a new
`start_workspace` command handles the Blox provisioning separately.

The frontend calls `onCreated(branch)` right away (closing the dialog
and showing the branch card in its "Provisioning…" state), then fires
`startWorkspace` in the background. The existing polling in
RemoteBranchCard picks up the status transition automatically.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
During initial workspace provisioning, Blox may briefly report status
"stopped" before transitioning to "running". Previously this caused
poll_workspace_status to persist the Stopped status and the frontend to
stop polling, leaving the card stuck showing "Stopped".

Now when the DB status is still Starting, a Blox "stopped" response is
treated as Starting so polling continues until the workspace actually
reaches Running.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@wesbillman wesbillman merged commit a31ea9a into main Feb 12, 2026
2 checks passed
@wesbillman wesbillman deleted the wesb/fix-new-branch-dialog branch February 12, 2026 01:26
taylorkmho added a commit that referenced this pull request Feb 12, 2026
* origin/main:
  feat: async worktree creation (#71)
  fix: Skip main worktree on project import and remove main badge UI (#70)
  feat(ui): replace long-press picker with explicit New note / New commit buttons (#67)
  fix: remember ordered list of recent agents instead of single last-used (#65)
  fix: capitalize 'Staged' in macOS application menu (#64)
  fix: dismiss new branch dialog immediately for remote branches (#57)
  feat: add Amp (Sourcegraph) as a supported ACP agent (#55)
  feat: restore subfolder autocomplete in new project dialog (#56)
  Consolidate ACP implementations into acp-client crate (#52)

# Conflicts:
#	staged/src/lib/BranchCard.svelte
#	staged/src/lib/NewSessionModal.svelte
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants