You should re-populate the working directory with the $GIT_DIR/info/sparse-checkout file content as follows: You cannot just disable “sparse checkout” because skip-worktree bits are still in the index and your working directory is still sparsely populated.
For example, to remove the file unwanted:Īnother tricky thing is fully repopulating the working directory when you no longer want sparse checkout. While $GIT_DIR/info/sparse-checkout is usually used to specify what files are in, you can also specify what files are not in, using negate patterns. If it turns from unset to set, that file will be removed. If skip-worktree turns from set to unset, it will add the corresponding file back. Then it compares the new skip-worktree value with the previous one. If an entry matches a pattern in this file, skip-worktree will not be set on that entry.
Git sparse checkout update#
When git read-tree needs to update the working directory, it resets the skip-worktree bit in the index based on this file, which uses the same syntax as. ” $GIT_DIR/info/sparse-checkout defines the skip-worktree reference bitmap. git read-tree and other merge commands native to git such as checkout, merge, or pull are useful in maintaining the skip-working tree bitmap and working directory update.Ī paraphrased quote from the manual here: Sparse-CheckoutĪ new feature called sparse checkout allows us to sparsely populate the working directory by using skip-worktree bit to inform GIT if the file in the working directory deserves a look. For the sake of illustration, let’s say we want to retrieve only the examples directory of the point cloud repo commited at the point cloud library git page. Well, starting from git 1.9, this feature is now part of git features. Have you ever been stuck trying to clone specific folders from a git repo recently?
0 kommentar(er)
