My question is – what is the workflow for the repository admin to do this?
@hwine You would navigate to https://github.com/apps/APPNAME and see something like this:
The “Evilizuzak-52” item is for my personal testing account. The “testrename2” is for an organization which I am not an owner of, but I am an external collaborator on one repository with admin access that is within that organization. So, that organization is listed as well. When I click on that item (“testrename2”) I see a form where the “All repositories” item is disabled and I can only select the repository I have admin access to from the dropdown.
Does that help? If not, can you clarify your specific situation – which integration, organization, user and repositories is this about?
No - that thread is about a completely different topic.
No, it’s not. But it’s somewhat easy to miss because the thread is a bit long. Please see: Adding an integration when not an admin
This specifically is for the use-case where you want to remove an installation from a repository you have admin access to, but you’re not an owner of the repository.
So, let’s say you follow the same flow as before – you go to https://github.com/apps/APPNAME and you’ll see something like this:
Notice the configure link next to the “testrename2” organization because the application is installed on at least one of the repositories that my account has access to (still the account that is not an owner but has admin access to one repository). Clicking that configure link leads to a 404 currently, as mentioned in that other issue, which is a problem that the team is investigating how to resolve.
Currently, it’s not possible for a repository admin to remove an installation from that repository – they need to ask an organization owner to remove it. Again, this is something that we want to improve.
Hope this helps, but let me know if I misunderstood anything.