What FastRepo
can see.

Start with Coverage

Settings → GitHub → Coverage prints what the last sync actually saw:

• the account you are signed in as
• how many repositories and accounts came back
• every FastRepo installation, marked all repositories or selected repositories only

An organisation absent from that list has not granted FastRepo access. That is the whole diagnosis.

GitHub App: private repositories follow the installation

The GitHub App is the normal setup. A private repository is readable only if FastRepo is installed on the account that owns it. Being a collaborator on the repository is not enough, and neither is being a member of the organisation.

Public repositories are visible without any installation, which is why a search can return dozens of results while every private repository is missing.

Fix: install FastRepo on that account, from Settings → GitHub → Manage repository access on GitHub.

Installed, but scoped to selected repositories

An installation set to selected repositories only hides everything outside its selection. The organisation shows up, its repositories do not. Add the repository to the selection on GitHub.

Fine-grained personal access tokens

A fine-grained token reaches only repositories owned by the single resource owner it was created for. It cannot see another account's repositories even when you are a collaborator there, and GitHub returns an empty organisation list for it. Create one token per owner, or use the GitHub App.

Classic personal access tokens

• repo to read private repositories.
• read:org to list your organisations. Without it, only organisations that own a repository you can read appear.
• Organisations that enforce SAML SSO need the token authorised for them.

Still missing something?

Send the Coverage lines to hello@solarbeam.studio. They say which side the gap is on.