{"version":"2.1.288","anchor":"teleport-bundle-upload-accepts-a-cwd","canonical_anchor":"teleport-bundle-upload-accepts-a-cwd","heading":"Teleport's git bundle upload now passes a working folder when none is given","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/teleport-bundle-upload-accepts-a-cwd","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Teleport's git bundle upload now passes a working folder when none is given\n\nWhen packing your repository for teleport, Claude Code now hands the bundling step a working folder if none was supplied\n\n**Unclear.** It is not clear what difference these two changes make to someone using teleport.\n\n**What**\n\nFor teleport, Claude Code uploads a git bundle, which is a single file holding a repository's history. The step that builds that bundle now receives a working folder (the directory the command runs from) when the caller did not supply one.\n\nOne of the results this step can report has been renamed from `bundle` to `not_served`.\n\n**Why**\n\nTeleport bundling may now work correctly when it is started from a different directory than before.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}