GitHub App shows correct repo access, but Railway "Connect Repo" returns "No repositories found"
taxhac
HOBBYOP

23 days ago

I'm trying to connect a private repo to a Railway service via GitHub, but the "Connect Repo" picker shows "No repositories found - try a different search" no matter what I do. Single-user setup — one personal GitHub account, no team or organization involved.

GitHub-side config (verified correct):

Railway GitHub App is installed with "Only select repositories" access, and the target repo is explicitly selected in that list

No pending permission-update banner on the installation page

Railway Account Settings → GitHub confirms the account is connected correctly

Repo details:

Private repo, owned directly by my personal GitHub account

Has active commits (updated within the last hour), not empty, has a default branch

What I've already tried (multiple times, including a full 5x repeat cycle):

Disconnected and fully uninstalled the Railway GitHub App from GitHub settings

Deleted/reconnected the GitHub integration from Railway's side

Re-selected the specific repo in the app's repository access list and saved

Searched for the repo directly by name in the Connect Repo dialog (not just browsing the list)

Confirmed only one GitHub identity is involved — no team workspace, no org

Despite all of the above, the picker still shows zero repositories. Given the config is verifiably correct on the GitHub side, this looks like it could be a stale server-side GitHub App installation/repo linkage on Railway's end — I've seen a similar exact symptom described in other threads here.

Could someone take a look at the backend linkage for my account and clear/refresh it if needed? Happy to share account/repo specifics privately if that's easier.

Solved

2 Replies

Railway
BOT

23 days ago

Your GitHub account is linked and the Railway App installation looks correct on our end. One step that differs from the uninstall/reinstall cycle you've already done: in your project canvas, click Add then GitHub Repository, and use the Refresh button in that picker to force a server-side cache refresh of your installation's repo list. If the repo still does not appear after that, try connecting it via the Railway Public API using the mutation with your username/repo-name to bypass the picker entirely.


Status changed to Awaiting User Response Railway 23 days ago


Railway

Your GitHub account is linked and the Railway App installation looks correct on our end. One step that differs from the uninstall/reinstall cycle you've already done: in your project canvas, click **Add** then **GitHub Repository**, and use the **Refresh** button in that picker to force a server-side cache refresh of your installation's repo list. If the repo still does not appear after that, try connecting it via the [Railway Public API](https://docs.railway.com/integrations/api/manage-services#connect-a-service-to-a-repo) using the mutation with your `username/repo-name` to bypass the picker entirely.

taxhac
HOBBYOP

22 days ago

That actually worked. Once I added it via the button, it also showed up via the main module.


Status changed to Awaiting Railway Response Railway 22 days ago


Status changed to Solved taxhac 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...