What FastRepo can see
FastRepo lists what your GitHub credential grants, and nothing else. It never searches GitHub globally. When an item is missing, one of the cases below explains it.
Start with Coverage
Open Settings, tab GitHub, section Coverage. It prints what the last sync 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 granted FastRepo no access. That is the whole diagnosis.
Read the symptom
| What you see | Cause | Fix |
|---|---|---|
| Public repositories only, no private one | FastRepo is installed on no account that owns them | Install it on each owner account |
| The organisation is listed, its repositories are not | The installation is on selected repositories only | Add the repositories to the selection |
| No organisation at all | A fine-grained token, which lists none | Use the GitHub App, or a classic token with read:org |
| A repository you were just invited to | The local list is up to a minute old | Type its name; the live search fetches it |
Browser sign-in: your account's view
The default connection reads what your GitHub account can see: your repositories, your collaborations, and every organisation you belong to, private repositories included. Nothing to install per organisation.
One exception: an organisation can restrict third-party OAuth apps. Its repositories stay hidden until an owner approves FastRepo under the organisation's OAuth app access settings on GitHub.
GitHub App: private repositories follow the installation
The GitHub App is the minimal-permissions alternative. FastRepo reads a private repository only when the app is installed on the account that owns it. A collaborator seat on the repository does not grant it, and neither does membership of the organisation.
Public repositories need no installation. That is why a search can return dozens of results while every private repository is missing.
Fix: Settings, tab GitHub, Manage repository access on GitHub. Install FastRepo on that account.
Installed, but scoped to selected repositories
An installation set to selected repositories only hides everything outside its selection. The organisation appears, its repositories do not. Add the repository to the selection on GitHub.
Fine-grained personal access tokens
FastRepo 1.1 no longer offers token entry. A connection made with a token in 1.0 keeps working until you reconnect; the two sections below explain what such a token can list.
A fine-grained token reaches only the repositories of the single resource owner it was created for. It reads no repository of another account, even where you are a collaborator. GitHub also returns an empty organisation list for it, by design.
Create one token per owner, or use the GitHub App.
Classic personal access tokens
reporeads private repositories.read:orglists your organisations. Without it, only the organisations that own a readable repository appear.- An organisation that enforces SAML SSO needs the token authorised for it.
Where the list comes from
Each sync merges four GitHub endpoints and removes the duplicates:
/user/repos, every affiliation: owner, collaborator, organisation member./user/installationsand the repositories of each installation./user/orgs, for the organisations with no readable repository./user, for your own account row.
Only the first call must succeed. Each other source answers for some credential types only, so a failure there removes rows, it never breaks the sync.
Still missing something
Send the Coverage lines to [email protected]. They say which side the gap is on.