Use sparse-checkout to do a faster, shallow clone #7268
Merged
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.
@benbp and I chatted briefly after standup. The linter needs the full repository but not the full history. azure-sdk-for-net's clone was taking 4 1/2-6 minutes because it was grabbing the history which we don't need. Flipping over to a shallow clone dropped the clone time down to 1m 1s. I'd grabbed the build definition check directly from net's ci.tests.yml since that could eventually be a gotcha.