Add support for sparse-checkout mode in Git add command to resolve is… #233048
Conversation
This file contains 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
|
@microsoft-github-policy-service agree |
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 pull request addresses issue #213677 by adding support for sparse-checkout mode in VSCode's Git integration. The change ensures that when sparse-checkout is enabled, the git add command includes the --sparse flag, allowing files outside the sparse-checkout definition to be properly staged and committed.
How to test?
git clone --no-checkout https://myproject.gitor init a new repo;git sparse-checkout init;create a new file;
try to stage file with add button on resource state from git extension in source control.
Result: The file should be added to index with no problem!