{"version":"2.1.281","anchor":"enterworktree-can-resolve-a-repo-root-from-a-non-git-working","canonical_anchor":"enterworktree-can-resolve-a-repo-root-from-a-non-git-working","heading":"EnterWorktree can resolve a repo root from a non-git working copy (code path compiled out)","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/enterworktree-can-resolve-a-repo-root-from-a-non-git-working","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### EnterWorktree can resolve a repo root from a non-git working copy (code path compiled out)\n\nEnterWorktree gained a fallback for folders that are not git repositories, but it never runs, so behaviour is unchanged\n\n**What**\n\n`EnterWorktree` is the tool that moves a session into a git worktree, an extra working copy of a repository. Its code now includes a fallback to a `workingCopyRoot` when there is no git root. That branch is switched off in the built program and never runs. A related lookup elsewhere always finds nothing. The error message shown when a folder is the main working tree is unchanged.\n\n**Why**\n\nNothing changes for you in this version."}