You'll notice
Useful3 Signal3
Packaging work for a cloud session now recognises "behind remote" and can start from your local commit.
What's wrong with this entry?
Anonymous. No account, no email.
What
When packaging your work for a cloud session, being behind the remote is now distinguished from having otherwise diverged from it, using a merge-base check, and the caller can start from your local commit in that case instead of refusing. When ancestry cannot be determined it warns instead.
Details
- The message shown when a session could not be armed is now assembled from a table of reasons covering bundling being unavailable, the size limit being exceeded, and the fact that syncing files back to your machine is not supported on Windows yet, replacing one fixed sentence.
- No gate on the verdict change itself.
Evidence
syncing files back to this machine is not supported on Windows yet
Strings lifted out of the shipped bundle, so the claim above can be checked against them.