[Feature Request] Allow GitHub apps to be created privately across multiple orgs in an Enterprise #7439
Replies: 6 comments 13 replies
-
Hello, we also want this feature at our enterprise. Currently we have apps that we list as public, so that we can install them on multiple (in our case 8) organizations. |
Beta Was this translation helpful? Give feedback.
-
This seems to be a duplicate of https://github.com/orgs/community/discussions/24549 |
Beta Was this translation helpful? Give feedback.
-
Hi there! |
Beta Was this translation helpful? Give feedback.
-
We are currently working on such a feature as mentioned in our Roadmap |
Beta Was this translation helpful? Give feedback.
-
Hey folks - this is in final testing right now, to make sure it's working securely, with the goal of releasing it before Universe (i.e. in the next week and a half). Specifically this is the ability for an enterprise to own an application and make it available to just their organizations and members. Keep an eye out here and the changelog for details. |
Beta Was this translation helpful? Give feedback.
-
As promised - here we are! Feedback welcome |
Beta Was this translation helpful? Give feedback.
-
Currently to create a GitHub App across multiple orgs you need to make the GitHub App public or duplicate the App.
For Enterprise Cloud users that have multiple orgs this means exposing internal behaviours (the names and descriptions of GitHub apps) publicly.
Is it on the roadmap to allow GitHub Apps a 3rd visibility option, between Private and Public? One that would allow users make a GitHub App private across an Enterprise, or an explicit list of orgs?
Beta Was this translation helpful? Give feedback.
All reactions