21 days ago
My Railway account (login via GitHub) owns the workspace and I am the sole Admin. The service source repo is
branch staging, auto-deploy on push.
This setup has been unchanged for ~3 months and deployed automatically without issue.
Since yesterday (16 Sep 2026) every push is flagged "Deploy this commit from an external
contributor?" and sits in Needs approval, even though the commit author (GitHub Renato1596)
is the same GitHub account my Railway account is logged in with, and I am the workspace Admin.
Nothing changed on my side. Could you check whether a recent change to the external-contributor
approval affects this, and whitelist my workspace / correct the account-to-commit-author
association so my own pushes auto-deploy again?
1 Replies
21 days ago
On a private repo, a deploy waits for approval unless the GitHub account that pushed the commit is linked to a Railway account that is a member of the project or workspace. The most common reason this starts happening on a previously working setup is that the GitHub-to-Railway account link needs refreshing: go to your Railway account settings, disconnect and reconnect your GitHub account, and also check that the Railway GitHub App installation in your GitHub settings has no pending permission updates and still has access to the repo. After reconnecting, any already-pending deployments still need to be approved once from the deployments list, but future pushes should auto-deploy again.
Status changed to Awaiting User Response Railway • 21 days ago
14 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 14 days ago