Add missing plugins-cache option to dotnet nuget locals documentation #47582
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.
The documentation for
dotnet nuget locals
was missing theplugins-cache
option that is available in newer versions of NuGet/dotnet. This option allows users to list or clear the plugins cache directory, which is used to store NuGet plugin-related data.Changes made:
plugins-cache
to the list of validCACHE_LOCATION
values in the Arguments sectionall
option to include plugins cachedotnet nuget locals plugins-cache --list
dotnet nuget locals plugins-cache -c
The
plugins-cache
option has been supported in the NuGet client since it was added to handle plugin caching functionality. This documentation update ensures users are aware of all available cache location options.Fixes #45151.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.