NuGet package not visible in Organization Packages page unless adding RepositoryUrl property to project file

[terumimcintyre-freightways]

Select Topic Area

Bug

Body

Hi All,

I've pushed a NuGet package to my GitHub Organization using dotnet nuget push command. I get a successful "Your package was pushed" response.

Navigating to my Organizations Packages tab, I do not see anything listed.

I can however see the package using its specific url (e.g., https://github.com/orgs/{org_name}/packages/nuget/package/{package_name})

This behaviour mirrors another discussion I was looking at : https://github.com/orgs/community/discussions/150083

I've done what was suggested in this particular discussion & added a RepositoryUrl property to my solutions csproj file. This pattern seems to hold as my original package is now listed in Organization > Packages.

Is this a feature or a bug? Subsequent packages pushed to my Organizations Packages do not appear in the UI unless I add the RepositoryUrl property in each project file.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[devstar222696]

Hi, @terumimcintyre-freightways.

This is a current GitHub Packages UI/indexing quirk (effectively a bug) for NuGet packages. Packages pushed to an organization may not appear under Organization → Packages unless they’re associated with a repository. Adding RepositoryUrl (or manually connecting a repo in the package settings) makes them show up, which is why your fix worked.

What to do (recommended):

• Add a repo link automatically via a shared Directory.Build.props:

<Project>
  <PropertyGroup>
    <RepositoryUrl>https://github.com/{org}/{repo}</RepositoryUrl>
  </PropertyGroup>
</Project>

• For already-published packages, open the package page → Settings → Connect repository.
• If visibility still lags, republish or regenerate the token used to push (some users report this refreshes indexing).

It’s not a publishing error on your side. Until GitHub resolves the listing behavior, link each package to a repo (preferably via Directory.Build.props) to ensure it appears in the org Packages UI.