Skip to content

fix: propagate real error when machineBash fails in createWorktree#1115

Open
AlseinX wants to merge 1 commit intoslopus:mainfrom
AlseinX:fix/issue-1110
Open

fix: propagate real error when machineBash fails in createWorktree#1115
AlseinX wants to merge 1 commit intoslopus:mainfrom
AlseinX:fix/issue-1110

Conversation

@AlseinX
Copy link
Copy Markdown

@AlseinX AlseinX commented Apr 17, 2026

Summary

  • createWorktree now differentiates RPC/communication failures (exitCode === -1) from genuine "not a git repo" errors, propagating the real error message instead of always reporting "Not a Git repository"

Test plan

  • From web client, attempt worktree creation on an offline machine → should show "Failed to reach machine" or RPC error, not "Not a Git repository"
  • From web client, attempt worktree creation on a non-git directory → should still show "Not a Git repository"

Fixes #1110

🤖 Generated with Claude Code

createWorktree unconditionally reported "Not a Git repository" for any
machineBash failure, hiding RPC errors and network issues. Now checks
exitCode === -1 (RPC/communication failure) and forwards the real error.

Fixes slopus#1110

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
m-bers added a commit to m-bers/happy that referenced this pull request Apr 18, 2026
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.

Web worktree spawn fails with 'Not a Git repository' — request never reaches daemon

1 participant