{"version":"2.1.247","anchor":"directory-sync-defers-unusual-layouts-with-a-remedy","canonical_anchor":"directory-sync-defers-unusual-layouts-with-a-remedy","heading":"Directory sync defers unusual layouts with a remedy","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/directory-sync-defers-unusual-layouts-with-a-remedy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Directory sync defers unusual layouts with a remedy\n\nUnusual checkouts are deferred with a plain reason and advice to use the main clone.\n\n**What**\n\nA new refusal reason covers checkouts that are linked working trees or keep their git directory elsewhere. Those sessions are deferred instead of probed, get their own preface saying nothing syncs back and the session cannot push to GitHub, and the remedy suggests starting from the repository's main checkout or an ordinary clone.\n\n**Details**\n\n- The reason is recorded as `layout_unserved`.\n\n**Evidence**\n\n`start from the repository's main checkout`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}