ensure proper casing for NuGet.Config
prior to any operations being performed
#11659
+51
−0
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.
NuGet only allows three options for the config file naming:
nuget.config
NuGet.config
NuGet.Config
If a code base is primarily developed on a case-insensitive file system like Windows, a config file named
Nuget.config
is fine, but dependabot runs in a Linux container with a case-sensitive file system and in that instance the config file won't be picked up by the NuGet tooling resulting in the default package feed ofapi.nuget.org
.This PR addresses that by running a script to rename the files prior to any operation being performed.
Fixes #11525.