Streamlining Access to GitHub Packages: A Scalable Solution for Large Organisations.

[iploooox]

Select Topic Area

Product Feedback

Body

The Problem with Granting Access to GitHub Packages at Scale

Let me set the scene: imagine you're managing 50 package containers across 100 repositories, all stored in GitHub Packages and built using GitHub Actions.

Quick math: that’s 5,000 checkboxes that I would need to manually click just to grant each repository access to those packages. This is not only tedious—it’s downright unmanageable.

And I’m not the only one facing this issue. There was even a related discussion that got ignored and eventually closed without a resolution.

As it stands, there's no public API available to handle this at scale. The only workaround we've found is a private API, essentially mimicking what the UI does:

curl -X POST https://github.com/orgs/<org>/packages/container/<package_name>/settings/bulk_add_actions_access \
  --data-raw 'authenticity_token=<token>&selected_ids=616984254'

A Proposed Solution

In my opinion, the smoothest and most scalable way to address this is to allow us to add a Team to a package. Every repository that the team has write access to, or has access to via the GitHub Actions token, should automatically gain access to that package.

This would save us from having to click through endless checkboxes and streamline package management for larger organizations. Let’s push for a more efficient solution here.

[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. ⭐

[jurgenweber]

How did you make the UI approach work? Is there more to the command? Any headers you set? Thanks