{"version":"2.1.280","anchor":"git-stash-create-now-passes-sparse-checkout-scoping-envargs","canonical_anchor":"git-stash-create-now-passes-sparse-checkout-scoping-envargs","heading":"Git stash-create now passes sparse-checkout scoping env\/args","tier":"internal","area":"Git Integration","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/git-stash-create-now-passes-sparse-checkout-scoping-envargs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Git stash-create now passes sparse-checkout scoping env\/args\n\nGit stash snapshots now respect sparse-checkout scoping instead of always stashing everything\n\n**Unclear.** The finding does not say exactly what the new `s` parameter contains or how it is determined, only that it feeds sparse-checkout related args and env vars into the stash command.\n\n**What**\n\nWhen Claude Code creates a git stash to snapshot uncommitted changes (for example before syncing a directory to the cloud), it now passes sparse-checkout related arguments and environment variables into the underlying `git stash create` command, based on a new parameter. Previously the stash was always created as a plain `git stash create` with no such scoping applied.\n\n**Why**\n\nSparse checkouts let a repository check out only part of its files. Without scoping, a stash snapshot could behave inconsistently with a sparse checkout's limited file set. Passing this information through keeps the snapshot behavior consistent with how the repository is actually checked out.\n\n- Area: Git Integration\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}