NuGet repository: evaluate prevent duplicates at upper group levels

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

🔥 Problem

When publishing a NuGet package to the NuGet Repository, we can toggle the nuget_duplicates_allowed setting at the Namespace-level Package Registry settings to control whether the duplicate packages are allowed to be published or not.

The issue is that we enforce duplicate checks only on the project level. To clarify, consider this group/project example:

/Group1
  /Project1
  /Project2

If the nuget_duplicates_allowed setting is false for Group1, the user can think that publishing the same package in Project1 & Project2 would be disallowed. However, this is not the case.

What's disallowed is publishing the same package in Project1 or Project2, but it's fine to publish the same package in both projects. The duplicate check is only done on the project level.

🚒 Solution

Evaluate the possibility of extending the functionality to the namespace/group level; meaning not allowing duplicates on the whole namespace/group level not just the project level.

This should be optional, so the user can decide whether the setting would be on the namespace/group level or the project level.