You'll notice
Useful3 Signal2
Starting a cloud session from a diverged repo now says why it began from GitHub, not your working tree.
What's wrong with this entry?
Anonymous. No account, no email.
What
Starting a cloud session from a repo that has diverged from its remote now prints the specific reason the session began from GitHub instead of your working tree, rather than starting silently.
Details
- Reasons computed: an operation already in progress, pull not supported, bundling unavailable, repository too large, or an explicit ref was requested.
- Each reason produces its own sentence, including one stating that file sync is off for that session.
- Windows gets a separate line saying syncing files back is not supported yet.
Evidence
and bundling is unavailable here, so the session started from GitHub without your local changes and file sync is off.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.