"GitHub Repo not found" after repo rename — branch detection broken but directory listing works
michaelachi
HOBBYOP
2 months ago
After renaming a GitHub repo, Railway shows "GitHub Repo not found" under
"Branch connected to production" but can browse the repo's directory tree
in the Root Directory selector.
Tried: disconnect/reconnect source repo, uninstall/reinstall Railway
GitHub app, verified repo access in GitHub app settings.
Auto-deploy on push no longer triggers.1 Replies
Railway
BOT
2 months ago
This is a known issue where renaming a GitHub repo can leave a stale reference on the service. To resolve it, go to your service's Settings tab, disconnect the repo under "Service Source," then reconnect it by selecting the repo under its new name and choosing the correct branch. Make sure to deploy the staged changes afterward so the webhook is re-established for auto-deploys.
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Open brody • 2 months ago