2 months ago
Account: wajd-badawi. Repo: wajd-badawi/wajd-os.
GitHub App is installed and repo access is granted, but the source picker returns no results — even when typing the repo name manually. Service shows "GitHub Repo not found" error. No Railway webhook exists on the repo. Auto-deploy on push to main has stopped.
Tried: disconnect/reconnect Account Integration, full uninstall/reinstall of Railway GitHub App, OAuth revoke and re-auth, toggling All vs specific repos, logout/login via GitHub.
Workaround: deploying via railway up --detach. The picker has never returned results through any of the above attempts. Appears to be a broken auth binding on Railway's side preventing repo listing entirely. Please reset the GitHub App integration for my account.
3 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
This is likely caused by outdated GitHub App permissions. We recently updated the permissions required by the Railway GitHub App, and installations that haven't approved the new permissions will see exactly these symptoms - empty repo picker and broken auto-deploys.
Please go to GitHub Settings -> Applications -> Railway App -> Configure, and look for a banner or prompt asking you to approve updated permissions. Once you accept them, your repos should appear in the picker and deployment triggers will be automatically restored.
If there is no permissions prompt and the issue persists after confirming the permissions are up to date, let us know.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Hi,
thanks for the response. I approved the updated permissions but there was no banner visible, I went through the configure flow anyway and it appears to have partially helped: the repo picker now shows wajd-badawi/wajd-os and I can select it.
However, the "Branch connected to production" section still shows "GitHub Repo not found" with a red error, and auto-deploy is not triggering on push. The repo is selected, the Railway App is installed on wajd-badawi with all-repository access, and my Railway account is connected as wajd badawi.
For context: this repo was transferred from a different GitHub account (wajd-os) to wajd-badawi in late March. It's possible Railway still has a stale internal reference to the old account.
Currently deploying manually via railway up as a workaround. Any further steps to fully restore auto-deploy?
Thanks
Attachments
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open nico • about 2 months ago
2 months ago
Hello wajd,
one thing i think you haven't tried yet ,in your service settings, hit the "disconnect" button next to the repo name (visible in your screenshot), then re-select wajd-badawi/wajd-os from the picker fresh, this is different from the account-level reconnects you already did. doing it at the service level should force railway to re-register the webhook and clear whatever stale reference is causing the "github repo not found" error on the branch section
Hope this help you :)