{"version":"2.1.282","anchor":"new-error-for-legacy-format-committed-trees-in-bundle-upload","canonical_anchor":"new-error-for-legacy-format-committed-trees-in-bundle-upload","heading":"Cloud uploads explain old-format git folders instead of failing vaguely","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/new-error-for-legacy-format-committed-trees-in-bundle-upload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud uploads explain old-format git folders instead of failing vaguely\n\nWhen uncommitted work can't be captured because git stored a folder in an old format, the upload now says so and how to fix it\n\n**What**\n\nWhen Claude Code uploads your repository for a cloud session, it also captures work you have not committed yet. Some older tools recorded a folder in git in a format that git can still read but no longer writes, for example with entries out of order or an unknown file mode.\n\nIf capturing your work runs into such a folder, the upload now fails with a specific explanation. The message tells you to commit a change in that folder and try again. Before this change, this failure produced a general message saying that setting your work aside had failed.\n\n**Why**\n\nIf your repository was written by older tools, you now get an error that tells you what to do.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}