You'll notice
Useful3 Signal2
Cloud sessions now name the exact reason your local checkout could not be reproduced, plus the fix.
What's wrong with this entry?
Anonymous. No account, no email.
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.