{"version":"2.1.247","anchor":"git-bundle-upload-failures-now-include-the-remedy-separately","canonical_anchor":"git-bundle-upload-failures-now-include-the-remedy-separately","heading":"Git bundle upload failures now include the remedy separately from the error","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/git-bundle-upload-failures-now-include-the-remedy-separately","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Git bundle upload failures now include the remedy separately from the error\n\nFailed uncommitted-change uploads now carry advice separately from the raw git error.\n\n**What**\n\nWhen a cloud session cannot package your uncommitted changes for upload, the failure now carries a separate `advice` field alongside the raw git error, so tools can show you what to do about it rather than just what broke.\n\n**Details**\n\n- Covers the two recoverable stash failures: a changed file whose name is not valid UTF-8, and the generic \"could not capture uncommitted changes\" case.\n- No gate; applies to any session that uploads a git bundle.\n\n**Evidence**\n\n`A changed file in this checkout has a name`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}