Feature request: Support organization roles and app permissions for internal repositories only

[jackivanov]

Select Topic Area

Product Feedback

Body

Hi GitHub team,

It would be great if organizations could define roles that grant permissions (read, triage, write, maintain, etc.) to all internal repositories without also granting those same permissions to private ones.

Right now, managing access at scale is tricky since the “all repositories” option applies to both internal and private repos, and “selected repositories” requires constant updates. Having an option to target only internal repositories would make it much easier to manage organization-wide contributor access while keeping private repos restricted to specific teams.

Similarly, it would be helpful if GitHub Apps could support the same access model, such as:

• All repositories
• Selected repositories
• All internal repositories

That last option would be especially useful for internal tooling and CI/CD apps that should have visibility only within internal repos, not private ones.

Thanks for considering it, this would really simplify access management for enterprise orgs.

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

[queenofcorgis]

Hi @jackivanov 👋🏼 ,

Thanks for submitting this thoughtful product feedback. Have you checked out our Well Architected Framework guide for Rulesets Best practices? This may not solve what you're looking for exactly, but may help you out.

The GitHub Well-Architected Framework is an open source-style, community-driven framework to curate the best way to deploy the GitHub platform. Learn more at https://wellarchitected.github.com/

[jackivanov]

@queenofcorgis I appreciate you sharing the Well-Architected Framework. I skimmed through it but couldn't find anything that helps with managing app installations at scale.

To clarify our request: we're very interested in having a way to select which repos an app is installed on using custom properties or repo visibility type. This would make managing apps at our scale significantly easier.