Check Repo Access
Can floo reach this repo, and if not, exactly why?
Answers the install question without minting a setup token or creating an
app. Authorization may complete an already observed setup intent. Causes
are distinguished only inside installations the org is authorized for;
see _authorized_repo_access.
Authorizations
A floo_ API key.
Headers
Organization to act in; defaults to the one joined most recently.
Query Parameters
Full repo name (owner/repo)
Response
Successful Response
Response from GET /v1/github/check-repo-access.
Why floo can or cannot reach a repository, as one distinguishable cause.
accessible: false on its own is what made first-time setup opaque: the
three causes below need three different actions, and collapsing them left
the operator re-running an install that had already succeeded (#2293).
ok, app_not_installed, repo_not_in_installation, repo_not_accessible