Recursively add SetAction to dotnet nuget subcommands#52270
Merged
tmat merged 1 commit intorelease/10.0.2xxfrom Dec 23, 2025
Merged
Recursively add SetAction to dotnet nuget subcommands#52270tmat merged 1 commit intorelease/10.0.2xxfrom
tmat merged 1 commit intorelease/10.0.2xxfrom
Conversation
This was referenced Dec 22, 2025
tmat
approved these changes
Dec 23, 2025
Member
|
/ba-g winrt |
This was referenced Jan 28, 2026
This was referenced Feb 12, 2026
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
2 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.
Fixes: #52220
In a previous refactoring PR #51624, there was a missing SetAction to dotnet nuget trust subcommands that broke them.