a month ago
After transferring our repo from a personal account (MarcD-SmartDMS/SmartDMS) to an org (SmartDMS-LLC/SmartDMS), the service's 'Branch connected to production' shows 'GitHub Repo not found' and won't let us select a branch. We've reinstalled the Railway GitHub App on the org (scoped to the repo), removed the org's OAuth app restrictions, re-selected the repo in Source settings, and disconnected/reconnected the GitHub account integration. GitHub-triggered deploys from the org repo succeed — only the branch setting is broken. Project: grand-comfort, service: SmartDMS (backend).
Pinned Solution
a month ago
Since the autodeploys are working, the GitHub webhook is fine. The Railway dashboard is probably just caching the old repo path from your personal account and failing to load the branch list.
Two quick things you can try to force it to sync:
Go to Service Settings -> Source, fully disconnect the repo from the service, and link it again using the new Org path (SmartDMS-LLC/SmartDMS).
Go to GitHub and quickly toggle the repo visibility (change to private/public and back). This usually triggers a fresh sync event through the Railway App and unfreezes the dropdown.
1 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Since the autodeploys are working, the GitHub webhook is fine. The Railway dashboard is probably just caching the old repo path from your personal account and failing to load the branch list.
Two quick things you can try to force it to sync:
Go to Service Settings -> Source, fully disconnect the repo from the service, and link it again using the new Org path (SmartDMS-LLC/SmartDMS).
Go to GitHub and quickly toggle the repo visibility (change to private/public and back). This usually triggers a fresh sync event through the Railway App and unfreezes the dropdown.
Status changed to Solved medim • about 1 month ago