Clean up code that was referring to sparse-check our always_exclude#261
Merged
kewillford merged 3 commits intomicrosoft:masterfrom Sep 14, 2018
Merged
Conversation
wilbaker
approved these changes
Sep 12, 2018
kewillford
force-pushed
the
cleanup_sparse_exclude
branch
from
d293ed8 to
cf26b8f
Compare
kewillford
force-pushed
the
cleanup_sparse_exclude
branch
from
cf26b8f to
a1fb40f
Compare
sanoursa
approved these changes
Sep 13, 2018
|
Does this mean that this documentation is also out of date? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Since VFSForGit no longer is using the sparse-checkout or always_exclude to track files and folders and instead is using the ModifiedPaths, this cleans up where we were incorrectly referencing them or the code was no longer used.