#Git sparse checkout update

The skip-worktree bit is not exclusively used for sparse-checkout but it's rather a tool in git's toolkit.

The reasoning behind this is quite simple. The easiest approach certainly being the suggestions from VonC. You can read about it here.ДЄs such you have to remove the skip-worktree bit manually from the files in question. When disabling sparse-checkout, or deleting the pattern file, this bits will still be set and the files won't return. When using sparse-checkout git will apply this bit to all files which do not match the patterns described in your sparse-checkout file. Git's sparse-checkout makes use of the skip-worktree bit, which basically tells git to consider the file in your working directory to be 'up to date', regardless of the true state. While VonC's answer is certainly correct and will help with the imminent problem, I feel the need to elaborate and explain the underlying issue. git/info/sparse-checkout (to checkout and track additional files) can be achieved with git read-tree -dry-run HEAD

git/modules//info/sparse-checkoutД«raham-snyder adds in the comments that updating a. The article 'Adventures in Git - SparseCheckouts' by Rich Somerfield propose a similar option (also valid for submodules): echo '/*' >. # Wipe out all traces of sparse checkout support You can see an example of 'undoing' a sparse checkout in this script by Roscoe A. Leaves the sparse-checkout file intact so a later git sparse-checkout init command may return the working directory to the same state. More precisely, as noted in Tao's answer:Дisable the core.sparseCheckout config setting, and restore the working directory to include all files.

#Git sparse checkout update

Update with git 2.25+ (Q1 2020), as I mentioned in 'Git sparse checkout with exclusion', you now have the git sparse-checkout command.