{"version":"2.1.248","anchor":"bundling-says-which-history-depth-it-could-use","canonical_anchor":"bundling-says-which-history-depth-it-could-use","heading":"Bundling says which history depth it could use","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/bundling-says-which-history-depth-it-could-use","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Bundling says which history depth it could use\n\nBundling a repo with partial history now explains which history depth it could use.\n\n**What**\n\nWhen Claude Code bundles a repository with incomplete history, it now explains which of the four possible outcomes applied, including the cases where the branch has no commits yet.\n\n**Details**\n\n- One case reports that nothing can be bundled at all, when the current branch has no commits and a local branch or tag has been cut.\n\n**Evidence**\n\n`HEAD is unborn and a local branch or tag is cut \\u2014 nothing can be bundled`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}