That's weird... Maybe try disconnecting your GitHub integration and reconnecting all together?

Thanks! I did several times :( It seems there is a cache somewhere in that part of the UI

Can you make sure you have given the Railway App bot access to the getkelo organization's repositories? Go to GitHub Settings -> Applications -> Railway App -> Configure -> Repository access, and confirm the repos you need are included. Then go to your Railway account and unlink and relink the GitHub integration once more after updating that access.

done! still the same. Looks like a cache not being invalidated

The stale repo list persists because the old GitHub account (FBisca) likely still holds an OAuth authorization for Railway. Go to FBisca's GitHub account, then Settings -> Applications -> Authorized OAuth Apps, find Railway, and revoke it. After that, go back to your Railway account and relink the GitHub integration as ropa03, and the repo list should refresh to show the getkelo organization's repositories.

done! now neither FBisca nor ropa03 repos appear in the list. I disconnect and connect again

Revoking the old OAuth cleared the stale FBisca list, so that part worked. When you reconnect GitHub on your Railway account, watch the GitHub OAuth prompt carefully: it shows a list of your organizations with a "Grant" button next to each one. Make sure you click "Grant" next to the getkelo organization during that authorization step, otherwise Railway won't have permission to list its repos.

Glad you found the issue! I guess I should've been more clear with what I meant with "disconnect your GitHub integration" 😅