chore: add NuGet.Config to pin restore to nuget.org only - #99
Merged
Conversation
Contributor
|
|
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.
Summary
Adds a repo-level
NuGet.Configthat clears all inherited package sources anddeclares only
nuget.orgas the authoritative feed.Problem
The global NuGet configuration on the development machine includes other
feed from an unrelated project. Every
dotnet restorein this repo contactedthat endpoint — generating
NU1900warnings and slowing down restores onmachines without access to that Azure DevOps organisation.
Change
NuGet.Configat repo root: