3 months ago
After renaming a GitHub repo, auto-deploy on push stopped working. The service connects to the repo without errors, but pushes to main don't trigger builds.
This matches the issue Angelo acknowledged in this thread (https://station.railway.com/questions/github-auto-deploy-stops-triggering-after-failed-builds) — auto-deploys silently stop triggering because upstream GitHub API requests are not handled gracefully.
What we've tried (all unsuccessful):
- Disconnect and reconnect the repo in service Settings (multiple times)
- Uninstall and reinstall the Railway GitHub App on GitHub
- Revoke Railway's OAuth authorization on GitHub and re-login
- Log out of Railway entirely and log back in via GitHub
- Verified GitHub App is installed with correct permissions and repo access
2 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Open Railway • 3 months ago
2 months ago
If you have the affected service opened and do a Cntrl + K -> Deploy latest commit, does it deploy the latest changes?
Other than that, I would suggest deleting that service and re-adding a new one linked to that repo, just be careful since this is a destructive action.
2 months ago
Received a note from Railway -- key was to keep the repo disconnected for awhile.
Status changed to Open medim • about 2 months ago
Status changed to Solved medim • about 2 months ago