GitHub auto-deploy broken after force push - "Connected branch does not exist"
hknobbe
PROOP

3 months ago

After a force push on my hknobbe/boodschappr-v2 repository, automatic deployments stopped working. The dashboard shows "Connected branch does not exist" for the main branch, even though it exists on GitHub.

What I've tried:

  • Disconnecting and reconnecting the repo and branch
  • Creating a new service
  • Uninstalling and reinstalling the Railway GitHub App on GitHub
  • Creating a completely new GitHub repo (boodschappr-app)
  • Pushing to new branches

Other repos on my account work fine with Railway. The issue is only with this specific repo.

Could you reset the repo/branch cache on your end?

Solved

1 Replies

sam-a
EMPLOYEE

3 months ago

This is caused by a cached reference to your old GitHub App installation. It should clear automatically within a few hours. After that, disconnecting and reconnecting the repo from Railway's dashboard should work.

If you need this solved sooner, let me know and I can see if we can invalidate the cache.


Status changed to Awaiting User Response Railway 3 months ago


Status changed to Solved hknobbe 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...