Fix a typo in expressions usage of properties instead of parameters#14749
Merged
akoeplinger merged 2 commits intodotnet:mainfrom May 3, 2024
Merged
Fix a typo in expressions usage of properties instead of parameters#14749akoeplinger merged 2 commits intodotnet:mainfrom
akoeplinger merged 2 commits intodotnet:mainfrom
Conversation
chcosta
previously approved these changes
May 2, 2024
Member
|
Sorry, would you mind also fixing this in eng/common/templates-official/steps/publish-pipeline-artifacts.yml? |
Contributor
Author
|
@dotnet-policy-service agree |
Contributor
Author
No problem, done. |
chcosta
approved these changes
May 2, 2024
akoeplinger
approved these changes
May 3, 2024
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
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.
My Custom Azure Pipelines VSCode Extension found this problem under the copy inside dotnet/runtime
As long properties is not defined, azure pipelines will happily ignore this typo, my extension throws an validation error
To double check: