Skip to content

Requests for NuGet packages that are not found on GitLab should be forwarded to nuget.org

Problem to solve

C#/.NET developers often use a combination of private, in-house built packages and packages that are publically available in the public NuGet registry.

However, we do not currently help users with pulling packages from this popular, remote repository.

Intended users

User experience goal

  • By default (although an Admin can turn the feature off) GitLab will look for packages first in the project/group/instance level NuGet registry, but if a package is not found, we will look in nuget.org to see if it can be resolved.

Proposal

When a user tries to download a NuGet package using their Project/Group/Instance-level endpoint and the package is NOT found, forward the request to nuget.org and, if possible, download the package.

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

Links / references