Skip to content
GitHub App has repository access but Railway cannot discover private repository
piotrjasak-spec
OP

a month ago

Railway cannot discover a private GitHub repository even though the Railway GitHub App is installed for the organization and the repository is explicitly selected in the app configuration.

Repository: LumenProjectOfficial/lumen-owner-memory-adapter

Existing Railway service: duea-registry-readonly-inspector

Existing source binding is still preserved and points to:

Branch: duea/pg18-readonly-inspector-20260922

Commit: 5824c24a6ae7cf70d74e9a4d6d44bc5533f16e09

GitHub App repository access is configured as “Only select repositories”, with this repository selected. I re-saved the GitHub App configuration.

Railway UI still reports:

  • Could not load branches. Retry
  • No repositories found - try a different search
  • Auto deploy unavailable

Refresh does not resolve the problem.

An API attempt to reconnect the same source also returns:

Repository "LumenProjectOfficial/lumen-owner-memory-adapter" not found or is not accessible

For troubleshooting, I staged a source disconnect but did NOT deploy it. The pending changes were discarded and the original source binding remains intact. No service redeploy or database restart was performed.

Could you please check whether the Railway GitHub App installation/repository authorization is stale or not being recognized by Railway, and advise how to refresh the integration without redeploying or changing the existing service?

I found a similar Railway Central Station case recommending unlinking and relinking the GitHub account integration to force a sync. Before doing that, please confirm whether this is safe for existing production services and whether it can be done without triggering a redeploy or altering their current source bindings.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 2 months ago


sam-a
EMPLOYEE

a month ago

Unlinking and relinking the GitHub integration from your account settings is safe for your existing services. It does not remove or change their source bindings, and it does not trigger a redeploy. Your service duea-registry-readonly-inspector stays connected to LumenProjectOfficial/lumen-owner-memory-adapter on branch duea/pg18-readonly-inspector-20260922 throughout.

The repository and branch pickers rely on your account's GitHub link to discover what you can access. Relinking refreshes that link, so it is the step to take after confirming the repo is selected under GitHub Settings -> Applications -> Railway App -> Configure -> Repository access, which you have already done.

Once relinked, opening the service's source settings to check that branches load is read-only. Only applying a staged source change would deploy anything.


Status changed to Awaiting User Response sam-a • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...