Under the hood
Worktree fast-resume now checks the worktree is verified before resetting, and handles reset failure more safely
What
When resuming a git worktree (a separate working copy of a repository) quickly, the code now:
- builds its git environment per working directory instead of sharing one environment across worktrees
- adds a
--separator to thegit reset --hardcommand, which prevents a branch or ref name from being misread as a file path - checks that the worktree is in a verified state with no pending marker before attempting the fast reset
- on reset failure, returns nothing and logs a warning instead of silently continuing as if the reset had worked
Why
These changes make worktree resume safer: a failed or unverified reset no longer proceeds silently, which could otherwise leave a worktree in an unexpected state without any warning.