Feature request: Support organization roles and app permissions for internal repositories only #179101
Replies: 3 comments
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
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/ |
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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:
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.
Beta Was this translation helpful? Give feedback.
All reactions