You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.238,
ImprovementsSection of the release
What
When 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.
Details
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.
Each reason comes with an action, for example "push the branch, or fetch it if GitHub already has it".
Evidence
this checkout is on a detached HEAD, which a session cloned from GitHub cannot start from
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
