I moved a project from one Hobby workspace to another (both mine — switching from a personal identity to a company one). Since the transfer, every push creates a Deployment Request:

"User isn't on the Railway team, so their commit needs approval. Invite them to bypass this requirement."

Railway displays a generic "User" instead of resolving the commit author's GitHub account.

What I have already verified — all correct:

The commit author's email is Primary + Verified on the GitHub account that owns the Railway workspace.

GitHub correctly attributes the commits to that account (avatar + username appear in the repo's commit list).

Railway → Account → Integrations shows "Connected as" that same GitHub account.

The Railway GitHub App is installed on both the organization holding the repo and the personal GitHub account.

Service source, branch, and "Auto deploys when pushed to GitHub" are configured correctly.

Commits contain no co-authors.

The commit author is the owner of the Railway workspace — same identity.

So the author and the workspace owner are one and the same, yet Railway treats the commit as coming from an outside contributor. "Invite them" is unusable, because member invites require the Pro plan.

Question: how do I make Railway recognize the workspace owner as a team member after a cross-workspace project transfer on Hobby? Is there a way to re-sync the GitHub identity ↔ workspace membership without upgrading to Pro?