{"version":"2.1.238","anchor":"cloud-sessions-explain-exactly-why-your-checkout-could-not-b","canonical_anchor":"cloud-sessions-explain-exactly-why-your-checkout-could-not-b","heading":"Cloud sessions explain exactly why your checkout could not be reproduced","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/cloud-sessions-explain-exactly-why-your-checkout-could-not-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Cloud sessions explain exactly why your checkout could not be reproduced\n\nCloud sessions now name the exact reason your local checkout could not be reproduced, plus the fix.\n\n**What**\n\nWhen a cloud session cloned from GitHub cannot reproduce your local checkout, it now names the specific reason and the fix, rather than reporting a generic mismatch.\n\n**Details**\n\n- Covered reasons: uncommitted changes to tracked files, commits GitHub does not have, history that is unreadable or shallow, a detached HEAD, and a branch with no remote-tracking ref.\n- Each reason comes with an action, for example \"push the branch, or fetch it if GitHub already has it\".\n\n**Evidence**\n\n`this checkout is on a detached HEAD, which a session cloned from GitHub cannot start from`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}