25 days ago
Every commit pushed to my private repo shows the "Deploy this commit from an external contributor?" approval prompt, even though all the standard causes are eliminated:
- My GitHub user owns the repo (not an org, not a collaborator on someone else's repo)
- My GitHub user installed Railway's GitHub App with access to this repo
- My GitHub user is the Railway workspace owner
- My Railway account's connected GitHub identity matches the repo owner
- The commit author email is verified on that same GitHub account
- "Wait for CI" is off in the service's Source settings
- No external co-authors on commits (verified — single author per commit, no
Co-Authored-Bytrailers)
Background: the service was originally created by a different GitHub user (a collaborator on the repo at the time). I've since disconnected and reconnected the GitHub source on the service while logged in as the repo owner, and the prompt still appears on the next push.
What is Railway actually checking to flag commits as "external contributor"? Which setting do I need to change so pushes from the repo owner auto-deploy?
1 Replies
Status changed to Open Railway • 25 days ago
2 days ago
Given that the service was originally created by another GitHub user, this looks more like stale GitHub-app/repo linkage state than a commit-author problem.
Railway’s own troubleshooting steps for GitHub autodeploy are:
- confirm at least one project member has a connected GitHub account with contributor access
- confirm the Railway GitHub App has access to the repo
- confirm the app has no pending permission updates
- wait a few minutes for Railway caches to refresh
- disconnect/reconnect the repo in service settings
- in the canvas use Add -> GitHub Repository -> Refresh
- if it still persists, uninstall and reinstall the Railway GitHub App
Because you already reconnected the source and the service used to belong to a different GitHub user, my strongest guess is stale app/repo cache or installation state, so I would specifically do the canvas refresh + full GitHub App reinstall next.