{"version":"2.1.274","anchor":"worktree-resume-git-reset-now-uses-separator-and-per-d","canonical_anchor":"worktree-resume-git-reset-now-uses-separator-and-per-d","heading":"Worktree resume: git reset now uses '--' separator and per-directory env; new verified-worktree check gates fast-resume","tier":"internal","area":"Git Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/worktree-resume-git-reset-now-uses-separator-and-per-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Worktree resume: git reset now uses '--' separator and per-directory env; new verified-worktree check gates fast-resume\n\nWorktree fast-resume now checks the worktree is verified before resetting, and handles reset failure more safely\n\n**What**\n\nWhen resuming a git worktree (a separate working copy of a repository) quickly, the code now:\n\n- builds its git environment per working directory instead of sharing one environment across worktrees\n\n- adds a `--` separator to the `git reset --hard` command, which prevents a branch or ref name from being misread as a file path\n\n- checks that the worktree is in a verified state with no pending marker before attempting the fast reset\n\n- on reset failure, returns nothing and logs a warning instead of silently continuing as if the reset had worked\n\n**Why**\n\nThese 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.\n\n- Area: Git Worktrees\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}