6 days ago
Hi
My railway appears to be configured to the new github org owned by the customer/stakeholder.
I can see the org in my railway, but as im not the owner of the org I cannot confirm the repo.
The owner shows their github repo is connected to Railway, but its not what Railways states in the source. It showed the retired repo.
Please can you help
2 Replies
6 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 6 days ago
6 days ago
Try reinstall github app on the github orgs and select repos you want to deploy
6 days ago
- Disconnect the "Retired" Repo (Your Action)
Before Railway can see the new repository, you need to force it to "forget" the old one.
Go to your Railway dashboard and open the affected Project.
Click on the specific Service that is stuck.
Navigate to Settings > Source.
Click Disconnect (or remove the GitHub connection).
- Configure GitHub App Permissions (Stakeholder's Action)
Even if the stakeholder sees Railway "connected" on their end, the Railway GitHub App needs explicit permission to access that specific repository within their organization.
Ask the stakeholder to go to their GitHub Organization Settings: Settings > GitHub Apps > Railway.
Click Configure.
Under Repository access, ensure it is set to either All repositories or Only select repositories (with the newly transferred repo explicitly selected).
- Reconnect the Source
Now that the old source is cleared and the permissions are set, the repo needs to be re-linked. Who does this depends on your access levels:
If you have access: Go back to Service Settings > Source in Railway, click Connect Repo, and search for the new organization's repository.
If you lack access: Because you are not the org owner, GitHub might still block you from bridging the connection. In this case, the stakeholder must log into the Railway project and connect the repository themselves. Once they authorize it, you will be able to manage the deployments as usual.
