Sparse Checkout #6394
Open
Sparse Checkout #6394
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
…ile diffing Signed-off-by: Jochen Hunz <[email protected]>
…used by sparse checkout code as well Signed-off-by: Jochen Hunz <[email protected]>
Signed-off-by: Jochen Hunz <[email protected]>
The sparse-checkout file is treated as a git_attr_file. A public API git_sparse_check_path reads the sparse-checkout file from the attribute file cache and checks the path against this attribute file using the gitignore ruleset Signed-off-by: Jochen Hunz <[email protected]>
…ed git_sparse object Signed-off-by: Jochen Hunz <[email protected]>
…es that are excluded by the sparse checkout ruleset - if sparse checkout is enabled Signed-off-by: Jochen Hunz <[email protected]>
Signed-off-by: Jochen Hunz <[email protected]>
…arse Signed-off-by: Jochen Hunz <[email protected]>
…accessed by checkout and diff functionalities quickly. Signed-off-by: Jochen Hunz <[email protected]>
Signed-off-by: Jochen Hunz <[email protected]>
…heckout Signed-off-by: Jochen Hunz <[email protected]>
Signed-off-by: Jochen Hunz <[email protected]>
…ries Signed-off-by: Jochen Hunz <[email protected]>
Signed-off-by: Jochen Hunz <[email protected]>
Signed-off-by: Jochen Hunz <[email protected]>
- Temporarily remove cone references, will need to revisit - Updating references in tests
seems we've run out of space on that enum...
YuKitsune
force-pushed
the
features/sparse-checkout
branch
from
6958e3f to
4224906
Compare
VinnyOG
pushed a commit
to 8thwall/libgit2
that referenced
this pull request
Jan 31, 2023
VinnyOG
pushed a commit
to 8thwall/libgit2
that referenced
this pull request
Mar 8, 2023
|
This PR seems really promising with lots of people wanting sparse-checkout support. Not just directly from the libgit2 community (#2263), but also from all of the other projects that are built with libgit2. Are there any particular blockers for merging this? The last update seems to be from 8 months ago. |
|
@YuKitsune @jochenhz Can you comment on the status of the sparse-checkout branch? It seems like work was done on it 1 or 2 years ago and it's not been pulled back into the main libgit2 repo. I tried using it to read a sparse repo and it failed during reading the index. Is it known to work? Are there known issues/limitations? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to implement basic sparse checkout functionality into LibGit2 building on @jochenhz's original PR.
What does it do?
sparse-checkoutfile is treated as anattr_file, hence followinggitignorerulescore.sparseCheckoutinit,set,add,reapplyanddisablecommands all supportedgit_sparse_check_pathto query whether or not a file is excluded from checkoutGIT_INDEX_ENTRY_SKIP_WORKTREEflag ongit_index_read_treebased on the sparse checkout ruleset.What does it not do?
core.sparseCheckoutConeGIT_CHECKOUT_NONEandgit_index_read_tree)Note