a month ago
I'm trying to connect a private GitHub repo to a Railway project as a
new service, but it doesn't appear in the "New → GitHub Repository"
search/picker — even though every other repo in the same organization
shows up fine.
What I've confirmed on GitHub's side:
-
The Railway GitHub App is installed on my organization
-
Repository access is set to "Only select repositories"
-
The repo in question is explicitly listed in the selected
repositories (confirmed via the repo's own Settings →
Installed GitHub Apps → Railway App → Configure)
-
I manually removed the repo from the selected list, saved, then
re-added it and saved again to force a fresh sync — no change
What I've tried on Railway's side:
-
Refreshing the repo list via the refresh icon in the New Service panel
-
Closing and reopening the New → GitHub Repository panel
-
Hard-refreshing the Railway dashboard
-
Pasting the repo's URL directly into the "paste a repo link" field
— still doesn't resolve it
Every other repo in the same org connects normally — this is isolated
to this one specific repo.
Is there a cache on Railway's backend for a specific repo/installation
that might need to be manually cleared? Happy to provide the project
ID or other non-sensitive details if that helps debug this.
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Since every other repository in the same GitHub organization appears normally, this is unlikely to be a general GitHub App permission problem.
You've already verified the relevant client-side state:
Railway GitHub App is installed on the organization
repository access is set to selected repositories
this specific repository is explicitly selected
removing/re-adding the repo in the GitHub App did not change anything
Railway's repo-picker refresh and hard refresh do not help
even pasting the repository URL directly does not resolve it
That strongly suggests Railway has stale or incorrect repository visibility/binding state for this specific repo.
There is a useful isolation test:
Create a temporary new Railway project and try New → GitHub Repository there.
If the missing repository appears in the new project, then GitHub authorization itself is healthy and the issue is isolated to the existing Railway project/service binding. Railway has seen this pattern before.
If it is still absent even in a brand-new project, Railway should inspect the GitHub App installation/repository sync for that organization and confirm that the installation token currently returned by GitHub includes this repo.
Railway-side checks should include:
current GitHub App installation_id for the organization;
repository list returned for that installation;
whether this repo's GitHub repository ID is present in Railway's cached installation/repository mapping;
whether a stale repo visibility/cache entry exists for the repo;
forcing a re-sync of that installation's repository list.
I would not keep reinstalling the GitHub App unless Railway confirms the installation itself is wrong. Since sibling repos from the same organization already work, repeated reinstall/relink attempts have low diagnostic value.