-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for sparse checkouts #680
Conversation
Bump @thboop? This would be extremely useful for repositories that check-in (somewhat) large artifacts, like their zipped dependencies, which is a somewhat common pattern with Yarn. |
This would be a great addition 👍 |
Ping @TingluoHuang? Are there any blockers? |
Remove test escape hatch Co-authored-by: Austin Pray <[email protected]>
Forgot to rebuild after merge
Shouldn't lfs.fetchinclude also be set or use "-I" (or "--include") parameter in GitCommandManager.lfsFetch to make sure LFS only fetches from included paths? |
Is any blocker exists? I'm eager to use this feature but wait for half a year. |
Any feedback from the maintainers? |
This would be great for monorepos y'know. |
Another friendly bump on this. +1 for this feature |
Hey everyone! I see that this PR has been frozen for a while... In my company we need to use the Here you can find a PR with an updated version to add support for the I have to mention that this PR has helped me in order to make mine so thanks @jonnelaaglandwinder to start this, let's hope we can finally have this functionality implemented! |
This PR can be closed due #1369 |
I've taken a crack at implementing a sparse checkout option suggested in #172.
It may prove useful for large monorepos, especially if a --filter option for fetch were to be implemented as well.
I've put a temporary escape hatch in the test script, since it would fail without the test data branch being present, but it should pass with those lines removed when the test data exists. (test-data/v2/sparse-checkout)