a month ago
Starting around 2026-08-31, every push to main started getting stuck at NEEDS_APPROVAL instead of auto-deploying. The approval screen says:
"User isn't on the Railway team, so their commit needs approval. Invite them to bypass this requirement."
I am the only member on this Railway team/project, and the commits in question are pushed under my own GitHub account on my own repo. I have no other members to invite, and there's no one else who could plausibly be "not on the team" here. This looks like a bug in whatever check maps the pushing GitHub identity to team membership — it's rejecting the project owner's own commits.
Commits are clean, single-author, no bots or co-authors.
The commit author matches my own GitHub identity, which owns and pushes to this repo.
Deploys before 2026-08-31 (e.g. 2026-08-13) auto-deployed fine, with no relevant team/member/permission changes made on my end in between.
There's no "Invite" action available to me that would resolve this, since I'm already the sole team member.
Please help, because this is absolutely slowing me down and I will need to switch providers if this will continue to happen.
1 Replies
a month ago
On private repos, a deploy requires 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 cause of this appearing for the project owner is a mismatch between the GitHub identity that authored/pushed the commits and the one connected to your Railway account (for example, a personal vs. work GitHub account, or a Git config with a different email/username than the GitHub account linked in Railway). Verify under Account settings that your connected GitHub account is the same one pushing the commits. If the repo is public, this check does not apply at all, so switching repo visibility is another option. Any deployment already stuck at NEEDS_APPROVAL still has to be approved once manually from the deployments list, but future pushes will auto-deploy once the linkage matches.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved dser • about 1 month ago