You'll notice
Useful4 Signal3
A cloud session seeded from your local files holds your first message until it confirms your changes arrived.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a cloud session is seeded from your local working tree rather than from the remote repository, the first message is now held until the session confirms your changes arrived. If it has not, sending is refused with an explanation that the session would otherwise be working from GitHub's copy of the repository; send again to go ahead anyway.
Details
- The hold is only armed for sessions seeded from an overlay of your local checkout. Sessions seeded any other way behave as before.
- A separate wording covers the case where you stopped waiting.
Evidence
the cloud session has not confirmed it has your local changes; send it again to go ahead regardless
Strings lifted out of the shipped bundle, so the claim above can be checked against them.