Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Hey there, yes, this is rather annoying (for users and us) - we're working on overhauling the connection logic we're using. The short term fix is to disconnect and reconnect GH to force us to discover the repo.

I've tried disconnecting and reconnected, but it's still not connected at all.

Is there an ETA of when this will be completed by?

We've created a ticket for this issue and it's currently in triage. We also noticed your workspace state is showing as inactive, which may be relevant - you can check your workspace status and billing in your dashboard settings.

This is a bug for me to and I need to make a critical deployment. I cannot see GitHub repo's to which I've given Railway access.

I have disconnected, reconnected. Nothing works.

Hello,

I sincerely apologize for the wait. It takes time to ensure everything is just right, but I’m pleased to announce that we have completely rewritten the way we retrieve the list of available repositories. This new approach is much more robust and provides real-time updates.

Please let us know if you continue to experience any issues, though!

Still doesn't work for me. I have deleted the Railway app in Github, tried to authorize again. And I still get "No repositories found" when I click the connect repo button.

I've gone through the configuration process multiple times now.

My second application that is connected to my repo, also shows "Repo not found error", but does deploy when I merge to main. (see screenshot)

For folks struggling with this, if you have railway CLI, you can still deploy manually with railway up -d --service <service-name> but I would prefer to have it pull from Github main branch on an MR merge, instead of relying on a manual deploy