Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Git IntegrationArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What
When 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.
Why
Sparse 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say exactly what the new `s` parameter contains or how it is determined, only that it feeds sparse-checkout related…
