before I try to address your question, I’d like to make clear some terminology: we distinguish between GitHub App creation and GitHub App installation. What your refer to seems to be an installation, because repositories are chosen at installation time. The creator of a GitHub App is the owner, and as long as the app is visible to the user installing, it could be installed in the user itself, or part of any organization the user may admin, or repositories the user may admin in that organization.
Currently, a GitHub App is created by one user who, during the time of creation, decides which repo they want to provide access to. Let’s say they chose only one repo which repo A.
I’m assuming we are talking about installing the GitHub App in an organization, and the user was either an org administrator, or a repository admin of A.
Now, if the repo admin of Repos B, C,D needs that app, they have no way of installing unless they are admins of Repo A or is the GitHub app creator themselves.
If the user admins those repositories B, C, and D, the user should be able to install the GitHub App on them, this is a feature we enabled recently. It’s being admin of Repo A for that user wouldn’t be a precondition either.
or is the GitHub app creator themselves
I assume you are referring as the user who installed the GitHub App in first place, which could again be either a repo Admin of A or admin or the target Organization.
Additionally if repo A admin, removes the app from their repo, then there is no way how they can add it back.
This shouldn’t be the case, unless the GitHub App requires permissions other than code (for example, a admin of repo A would be able to install it again if the app requires, say, “organization permissions”).
The App becomes “orphaned” and we need to wait for the creator , assuming not on vacation, to add the repo back.
I’m not 100% sure about this orphan situation, but I think the app should be removed in this case.
Therefore, is it possible for the app to be installed/associated with an Org by the creator. The repo admins in that org can then decide whether they need that app or not by going to settings -> integration and services -> searching for the app ?… just like how we can add a service, we should be able to add/install an app in the org ( I don’t want the app to go out of my org for other orgs to see them …
I’m not sure to follow your explanation, but I can say GitHub Apps have a target: this is either a User, or an Organization, so the installation should not transcend those boundaries.
I want it restricted only within my org but any repo admin in that org can install it as needed without depending on the creator ).
This should be the case: depending on the app permissions, repository admins may be able to add/remove repositories they admin.
Is this a fair request ?
It is! and we should supports the functionality you are referring to. If that’s not the case, that’s unexpected.