You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(in bash)
git init junction-test
cd junction-test
echo "**/ignored/" >.gitignore
mkdir dir1
mkdir dir2
echo bogus >a
echo bogus >dir1/a
echo bogus >dir2/a
git add .
git commit -m "base"
mkdir -p dir1/ignored/target
mkdir dir2/ignored
(now, in CMD)
mklink /J dir2\ignored\source dir2\ignored\target
(now, in any shell)
git sparse-checkout set
What did you expect to occur after running these commands?
git sparse-checkout set should have no error output and the only file in the working dir should be a. (In a more general case, the directories that live outside of the sparse-checkout should not exist.)
What actually happened instead?
$ git sparse-checkout set
warning: could not open directory 'dir2/ignored/source/': No such file or directory
warning: failed to remove directory 'dir2/'
$ ls
a dir2/
Context Notes
This example is contrived, but matches the behavior of an internal monorepo that uses junction points between shared contents of node_modules directories to save space when building Javascript components. This behavior is causing performance issues with the sparse index as alerted by the new advice message in Git 2.46.0.
The text was updated successfully, but these errors were encountered:
Setup
I'm using the
microsoft/git
fork, but I don't expect the problem to be in the code that is custom to that fork.defaults?
Details
Issue happens in Git Bash or CMD (though my setup requires CMD)
Minimal, Complete, and Verifiable example
this will help us understand the issue.
git sparse-checkout set
should have no error output and the only file in the working dir should bea
. (In a more general case, the directories that live outside of the sparse-checkout should not exist.)Context Notes
This example is contrived, but matches the behavior of an internal monorepo that uses junction points between shared contents of
node_modules
directories to save space when building Javascript components. This behavior is causing performance issues with the sparse index as alerted by the new advice message in Git 2.46.0.The text was updated successfully, but these errors were encountered: