Connected Github repo is in red and brunches "❌ Failed to fetch"

stepahin
HOBBY

4 months ago

I had one Production environment with a connected mono repository and the Main branch selected, with automatic deployment. I created a second Staging environment. Automatic deployment continues to work in both. I didn't change anything in GitHub except for new commits. But now, when I started thinking about creating a separate Staging branch (I haven't created it yet) and disabling automatic deployment in the Production environment, I went into the settings of the frontend and backend services and in both environments the connected repo is in red and branches show " Failed to fetch" and I can't select the branches. Although automatic deployment continues to work, the Railway connection in the repo settings on Github remains unchanged. I tried clicking Disconnect and then Connect Repo, and it immediately turns red again. What happened and how do I fix this?

Solved

1 Replies

stepahin
HOBBY

4 months ago

Solved. Thanks ChatGPT:

 Step 1: Refresh GitHub permissions on Railway

  • Go to your Railway dashboard:

    • Click on your profile icon (top right).

    • Click Account SettingsIntegrations.

  • Under GitHub, click Disconnect and then Reconnect your GitHub account.

    • Railway will request OAuth access again. Grant permissions to your repository and organization explicitly.

This usually solves 90% of the cases.


Status changed to Solved uxuz 4 months ago


Connected Github repo is in red and brunches "❌ Failed to fetch" - Railway Help Station