Setting Visibility/Access to NugGet Packages Pushed to GitHub Packages

[MattWalker414]

Select Topic Area

Question

Body

I have a repository where we place third-party .nupkg files, which when updated, launches a workflow, the main job of which is to push the packages to the Organization level - or I guess the home of GitHub Packages. All of that seems successful as I can access the packages there afterward.

The issue that arises is that I am the only one who can see the packages there and through Visual Studio's NuGet Package Manager. I know that I can go to each package's settings and set access, but that seems that it could become quite tedious if the number of packages we are working with increases.

I've read that there is no way to set some sort of global access using dotnet nuget push, but is there some global Organization setting that will allow GitHub packages to be accessed downstream?

I've also read that packages can be pushed to a repository, but I don't think it's as simple as pushing packages to a repository and have it function properly as a NuGet host. I believe an index.json needs to be applied and maybe some other, base metadata files.

So, in short, how can I make the NuGet packages I upload to GitHub Packages visible/accessible to our Dev team? Again, I'm trying to avoid any manual steps if possible and my thinking there is that there has to be some setting to allow this.

Newb, so any help is Greatly Appreciated!!

[Rishit-katiyar]

To ensure visibility and accessibility of NuGet packages uploaded to GitHub Packages for your Dev team without manual intervention, consider automating access settings using GitHub Actions triggered on package updates. Additionally, leverage your repository as a NuGet host by pushing packages directly and configuring it with necessary metadata files, such as index.json. Explore organizational settings at the GitHub Organization level to optimize package visibility. By combining automation, repository-based hosting, and organizational settings exploration, you can establish a streamlined solution for making NuGet packages readily visible and accessible to your Dev team.

[MattWalker414]

Tanks for the response!

The use of a repository was explored and I think that is the solution, but I have no idea what is also needed in the repository with regard to metadata files so that the repository will function as a valid NuGet feed. I do think that is my answer if I can only find the needed prerequisite metadata files.

If I can get that to work my build setup would be a repository holding .nupkg files which would be updated as needed. Via GitHub workflow they would be checked out and pushed to either the same repository functioning as a feed or to an different repo to serve as a feed for all of our packages, both proprietary and third-party.

[MattWalker414]

Is there a good resource to direct me in setting up a repository as a NuGet feed as opposed to uploading to GitHub Packages?