Your Railway account is now linked to the GitHub account dmik86, so the old dmik10k name is only your Railway username and no longer the connected GitHub login.

GitHub connections were revoked during the October 21 incident, and the fix for repositories that will not load is to reconnect GitHub in Account Settings, confirm the Railway GitHub App still has access to mint_street, then disconnect and reconnect the repository in the service's Settings and choose Deploy Latest Commit (Cmd+K, or Ctrl+K on Windows). If "Could not load branches" still appears after those steps, please share a screenshot of that screen and the exact step where it shows up.

I tried to resolve it many times. Using claude too. This is his final verdict

This is a Railway-side account problem, not something in your settings. You've done the right steps, so the next move is support.

We checked your account and it is linked to the GitHub login dmik86, so the account link itself is in place. One thing we did notice: the service linked to this thread is still connected to a repository under the old dmik10k owner name, not under dmik86.

Since reconnecting hasn't cleared "Could not load branches" for dmik86/mint_street, please share a screenshot of the screen where it appears, the name of the service you are connecting the repo to, and whether it happens when connecting a new repo or changing the branch on an existing one.