{"version":"2.1.247","anchor":"plain-language-reasons-when-an-unusual-git-checkout-is-refus","canonical_anchor":"plain-language-reasons-when-an-unusual-git-checkout-is-refus","heading":"Plain-language reasons when an unusual git checkout is refused","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/plain-language-reasons-when-an-unusual-git-checkout-is-refus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Plain-language reasons when an unusual git checkout is refused\n\nRefused checkouts now name the exact layout problem instead of failing vaguely.\n\n**What**\n\nCheckouts that upload or sync can now say precisely why they were refused: a broken `.git` file pointer, an administrative directory in an unexpected place, a back-link that does not point at the working tree, a mismatched common directory, a bad placement, or per-worktree configuration.\n\n**Details**\n\n- The back-link case suggests running `git worktree repair`.\n- Per-worktree configuration (`extensions.worktreeConfig` or a `config.worktree` file) is named as not supported by upload yet.\n- Replaces generic failures with a named reason per layout.\n\n**Evidence**\n\n`that uses per-worktree configuration (extensions.worktreeConfig, or a config.worktree file), which this upload does not support yet.`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}