Fix TestGitHubFolderCheckoutOptimization test expectation after checkout optimization #13577
+3
−3
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.
Test
TestGitHubFolderCheckoutOptimization/custom_checkout_keeps_github_sparsefailed because its expectation was outdated after checkout optimization logic was introduced in commit 7ab8281.Changes
custom_checkout_keeps_github_sparse→custom_checkout_skips_github_sparse.githubsparse checkout to be present (true) to expecting it to be skipped (false) when custom checkout steps existContext
The new optimization in
compiler_yaml_helpers.gocorrectly skips.githubsparse checkout when custom steps containactions/checkout, since the full repository checkout already includes.github. The test now validates this optimization works as intended.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.