Ensure assets resolution script handles special-case file paths #8831
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.
Basically, when we're merging a commit into another, we need there to be a "change" in a file so that
test-proxy pushworks without any weirdness.When the first file discovered contained
[or]powershell will break when attempting to add content to the file path. You have to call it out withLiteralPathto honor paths with these characters in it.Sorry for for the inconvenience @jalauzon-msft !