The messages around sending local files to a cloud session were rewritten so the outcome is explicit on both sides. A successful upload now states that files were uploaded for the cloud session, with correct singular and plural forms, a count of skipped files and the elapsed time in seconds, replacing the terse "Synced N files". Where files are left behind, the wording now names the reason, and a separate notice covers the case where the cloud session never applied what was sent.
- Success line reads
for the cloud session (${n} skipped) in ${r}s, so skipped files and duration are visible without inspecting anything else. - Untracked files are left behind and explained when the repository is hosted somewhere other than github.com, recorded internally as
unpinned_other_host, or when an explicit ref was passed on the command line, recorded asunpinned_explicit_ref. - A warning covers a cloud session that has not applied the uploaded files, most often because file sync is not enabled for the account yet, and states that changes made locally and in the cloud session may not reach the other side.
- The explanation for an empty repository was reworded, and a line was added noting that the upload is scoped to the current branch.
for the cloud session (${n} skipped) in ${r}s, "The cloud session has not applied the files uploaded from this directory (file sync may not be enabled for your account yet); changes made here and in the cloud session may not reach the other side"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.