[Vincent Biret (baywet)]

CFS users will get dependencies restoration issues in dotnet unless they remove the nuget.config locally. This pull request documents that so they get unstuck

after further discussions, this only carries the default configuration any dotnet user should have. And it's problematic for CFS users. So we'll simply remove the nuget.config file.

[Copilot]

Pull request overview

Updates contributor documentation to help Microsoft developers using CFS avoid .NET dependency restore failures caused by the repo’s local NuGet configuration.

Changes:

• Adds a CONTRIBUTING.md note for Microsoft contributors using CFS about removing dotnet/nuget.config before running dotnet restore.
• Clarifies that the change is local-only and should not be committed.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Suppressed comments (2)

CONTRIBUTING.md:122

• These commands will error if the file has already been removed. Using idempotent variants (and PowerShell error suppression) makes the instructions easier to follow.

    # macOS/Linux
    rm dotnet/nuget.config

    # PowerShell
    Remove-Item dotnet/nuget.config

CONTRIBUTING.md:124

• The term “CFS rewrite” (and the CFS acronym) isn’t defined anywhere else in this document. Consider expanding the acronym on first use or linking to a brief explanation so contributors know whether this applies to them.

This local-only change should not be committed. Removing the file allows the CFS rewrite to handle package feed rewriting correctly during `dotnet restore`.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.