{"version":"2.1.247","anchor":"start-up-explanations-for-unusual-checkout-shapes","canonical_anchor":"start-up-explanations-for-unusual-checkout-shapes","heading":"Start-up explanations for unusual checkout shapes","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/start-up-explanations-for-unusual-checkout-shapes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Start-up explanations for unusual checkout shapes\n\nCloud startup now explains unusual checkout shapes, including that nothing syncs back and pushes won't work.\n\n**What**\n\nThe messages shown when a cloud session starts gained two reasons covering a checkout made with `git worktree add` and one whose git directory sits outside the working tree. A linked working tree's changes are carried into the session, but nothing syncs back and the session cannot push to GitHub.\n\n**Details**\n\n- Whether you see these depends entirely on the shape of your checkout; there is no flag.\n\n**Evidence**\n\n`this checkout keeps its git directory outside the working tree (a .git file, or a git directory elsewhere), a shape this machine cannot yet compare with GitHub`\n\n- Area: Cloud Sessions\n- Names: `git worktree add`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}