Repository navigation
Windows: worktrees stay on the repo's side of the WSL boundary #434
Description
Follow-up to #397. electron/wsl.js and the wrapCommand/resolveSpawn seam landed (commit 4a21944). Remaining: setupWorktree in electron/worktrees.js joins worktreeBase (app userData, a Windows path) with the thread id. For a WSL-side project that puts the worktree on the Windows side of the boundary — and 'git worktree add' running through wsl.exe cannot even address it. Worktrees for a WSL-side project must land inside the distro, never under /mnt/c. Also: the gitOut/gitOutAsync helpers in worktrees.js must route through the wrap seam, and file watching on Windows must poll.
Activity
currentbits commentedon Aug 18, 2026
Merged into the #397 branch. WSL-side worktrees now land inside the distro at /.solenta/worktrees/ (/tmp/solenta-worktrees when the repo itself is on /mnt/), with the matching UNC stored as worktreePath so Windows-side existsSync still works. worktrees.js git helpers share one resolveGitCommand wrap: a UNC cwd becomes wsl.exe --cd and UNC path args are rewritten to linux paths. Known gap, marked with a ponytail comment: sweepOrphanWorktrees only scans the userData base, so WSL-side worktrees are not orphan-swept — thread-keyed cleanup still reaches them. Confirmed there is no file watcher today (status/diff on demand, PR refresh interval-polled), so the poll-watching half of the rule is a note, not code.