pub async fn get_integrations_github_installations(
configuration: &Configuration,
) -> Result<GithubInstallationsOut, Error<GetIntegrationsGithubInstallationsError>>Expand description
Lists the GitHub accounts the caller may see the App installed on, each confirmed against the App’s own list, plus where to add another. The confirmation is the point. A connection row holds an installation id, and an id whose installation was since removed on GitHub is a row that mints nothing — every list and import against it fails with a token error, which reads as "our git integration is broken" rather than "that install is gone". Checking the App’s view turns that into a fact the caller can act on. ORG-SCOPED for a tenant, deliberately. The App is installed across every customer, so the raw list is the customer list; a tenant sees only accounts its own org has bound. It discovers a NEW account by installing it (InstallURL), which is GitHub’s own consent screen — not by reading ours. A SUPER ADMIN sees the App’s whole install list, because that list is the platform’s own inventory rather than any one tenant’s data, and platform sudo is the single cross-tenant scope this house has. Without it an App installed out-of-band — granted straight from GitHub, so no connect flow ever ran and no connection row exists — is invisible to everyone: the console card reads "not connected" and an operator asked "which GitHub orgs do you see" can only answer for accounts already bound, which is precisely the accounts that were never the question.