Cloud teleport aborts rather than uploading if your folder's git data cannot be read.
What's wrong with this entry?
Before seeding a cloud session from a folder, teleport checks the folder can be vouched for. A .git entry that cannot be read as a git checkout now aborts session creation with an explanation rather than uploading. This path only runs when folder seeding is enabled by CCR_ENABLE_BUNDLE or its server-side flag.
- The refusal is recorded with reason
folder_seed_refusedand causegit_entry_unvouched. - A new bundle failure reason
refusedpasses its message through after stripping the leadingNot uploading this working tree:. - Advice from a failed stash is now forwarded into the rerouted-bundle failure text.
- The list of files left out is no longer included in the source-decision payload.
Not starting a cloud session from this folder: it has a .git entry that could not be read as a git checkout
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Cloud sessions can start from a plain folder, not just a git checkout
Both mention enable bundle
-
v2.1.242
The bundle is split into chunks loaded on demand
Both mention bundle
-
v2.1.242
Much of this release's diff is re-bundling, not behaviour
Both mention bundle