Private repo won't appear in Connect Repo picker despite correct GitHub App install
carbondrafting
PROOP

a month ago

I can't connect my repo to my service — it doesn't show up in Railway's Connect Repo picker.

What I've verified and tried:

  • The repo is private and I own it directly under my single personal GitHub account (not a collaborator, not an org, never transferred).
  • On GitHub, the Railway GitHub App IS installed with "All repositories" access and the repo is listed.
  • Railway connects via the GitHub App, so it correctly does not appear under Authorized OAuth Apps — checked that too.
  • I've disconnected/reconnected the source, fully uninstalled and reinstalled the Railway GitHub App from Railway's Connect Repo flow, hard-refreshed, and logged out/in. No change.

The GitHub grant looks correct on every check, but the repo still won't surface in the picker. Has anyone hit this, or is this a backend installation-to-workspace binding issue that needs Railway staff to re-sync? Service is currently Online on an older deploy; I just can't ship new deploys.

Solved

5 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


carbondrafting
PROOP

a month ago

Additional info: when I create a NEW Railway project, the carbon-dd-portal repo connects fine and appears in the picker. The repo only fails to connect on my existing service. This isolates the issue to the GitHub binding on my existing carbon-dd-portal service specifically — not my account or GitHub access. Please re-bind/re-sync the GitHub source on my existing service.


carbondrafting
PROOP

a month ago

Update with specifics. There is a contradiction Railway support needs to resolve on the backend:

  • Account → Integrations → GitHub shows ALL green: "Connected as CarbonDrafting", "Use GitHub to login to Railway", and "Railway App installed".
  • The repo IS connected at the service level (Source shows CarbonDrafting/carbon-dd-portal).
  • BUT the service shows "Auto deploy unavailable" with the tooltip: "No project member has access to this GitHub repository. Check if the GitHub Railway App is installed and project members have their GitHub accounts connected."

So my account-level GitHub connection reports fully connected, yet the service reports no project member has access. I've already tried: Configure, disconnecting/reconnecting the GitHub integration, uninstall/reinstall of the GitHub App, source disconnect/reconnect, hard refresh, and logout/login. The green account status and the service's "no access" error are inconsistent — this appears to be a backend state mismatch only you can reconcile. Please re-sync my GitHub installation/membership to this project so auto deploy works.

My service is Online on an older deploy, so no outage — I just cannot ship new deploys. Pro account, workspace carbondrafting, info@carbondrafting.com.


carbondrafting
PROOP

a month ago

Final confirmation of the issue: I opened the "2 changes to apply" modal and clicked "Deploy Changes" (the modal even says "carbon-dd-portal will redeploy"). Nothing happens — no deployment starts, no error. The two staged "changes" are no-ops anyway (Branch main->main, Repo CarbonDrafting/carbon-dd-portal -> same).

Summary of the state:

  • Account > Integrations > GitHub: ALL green (Connected as CarbonDrafting, Use GitHub to login, Railway App installed).
  • Service Source: repo connected (CarbonDrafting/carbon-dd-portal, branch main).
  • But the service shows "Auto deploy unavailable" with tooltip: "No project member has access to this GitHub repository..."
  • Every deploy path fails: auto-deploy on push does nothing, manual redeploy does nothing, applying staged changes does nothing.

My account reports fully GitHub-connected, yet the project reports no member has repo access. This is a backend state mismatch only Railway can reconcile. Please re-sync the GitHub installation/membership for this project so deploys can run. Pro account, workspace carbondrafting, info@carbondrafting.com. Service is Online on an older deploy (no outage); I just cannot ship new deploys.


carbondrafting

Final confirmation of the issue: I opened the "2 changes to apply" modal and clicked "Deploy Changes" (the modal even says "carbon-dd-portal will redeploy"). Nothing happens — no deployment starts, no error. The two staged "changes" are no-ops anyway (Branch main->main, Repo CarbonDrafting/carbon-dd-portal -> same). Summary of the state: - Account > Integrations > GitHub: ALL green (Connected as CarbonDrafting, Use GitHub to login, Railway App installed). - Service Source: repo connected (CarbonDrafting/carbon-dd-portal, branch main). - But the service shows "Auto deploy unavailable" with tooltip: "No project member has access to this GitHub repository..." - Every deploy path fails: auto-deploy on push does nothing, manual redeploy does nothing, applying staged changes does nothing. My account reports fully GitHub-connected, yet the project reports no member has repo access. This is a backend state mismatch only Railway can reconcile. Please re-sync the GitHub installation/membership for this project so deploys can run. Pro account, workspace carbondrafting, info@carbondrafting.com. Service is Online on an older deploy (no outage); I just cannot ship new deploys.

shrutkirti-kadam
HOBBY

a month ago

Hello, the same thing is happening to me, i guess this is just a error on their part


chandrika
EMPLOYEE

a month ago

Hi there! GitHub is currently experiencing an issue with app installation token authentication which is causing these errors. You can track it here: https://www.githubstatus.com/incidents/k5z4d1v1tqmt. No action needed on your end, deploys should recover once GitHub resolves this. Apologies for the trouble!


Status changed to Awaiting User Response Railway 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 28 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...