{"version":"2.1.284","anchor":"git-clones-with-sparse-paths-now-populate-files-with-read-tr","canonical_anchor":"git-clones-with-sparse-paths-now-populate-files-with-read-tr","heading":"Partial git clones now fill in their files a different way","tier":"internal","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/git-clones-with-sparse-paths-now-populate-files-with-read-tr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Partial git clones now fill in their files a different way\n\nWhen Claude Code clones only part of a git repository, it now fills in the files with git read-tree instead of git checkout\n\n**Unclear.** It is not confirmed which feature makes these partial clones, though plugin or marketplace sources are the likely one.\n\n**What**\n\nA sparse clone copies only some folders of a git repository. When Claude Code makes one, after choosing the folders it now fills in the files with `git read-tree -u --reset HEAD` instead of `git checkout HEAD`. If that step fails, the error now starts with \"git read-tree after sparse-checkout failed:\".\n\n**Why**\n\nThis is likely to fix partial clones where the checkout step did nothing or failed, which could leave the cloned folder without its files.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}