22 days ago
Hi Railway team.
I transferred my private GitHub repository from Dedher2/telegram-npc-game to ZaRusb/telegram-npc-game.
I reconnected Railway to GitHub as ZaRusb and authorized the Railway App specifically for ZaRusb/telegram-npc-game.
However, the existing Railway service worker in project pleasing-forgiveness is still stuck on the old source Dedher2/telegram-npc-game and shows GitHub Repo not found.
Clicking the edit/pencil icon for Source Repo only redirects me to GitHub App repository permissions, where ZaRusb/telegram-npc-game is already authorized. It does not allow me to select the new repository.
Please refresh or update the GitHub source binding for the existing worker service to:
ZaRusb/telegram-npc-game
Branch: main
Please do not create a new service and do not change variables, volume, domain, database, or trigger a deployment.
Project ID: f5932726-3108-47cf-8882-2e6f7ef05e9a
Service ID: 2fe25e49-bbf9-4a9b-85ce-0837d6f419c6
Environment: production
1 Replies
22 days ago
You can update the source repo on your existing service yourself without affecting variables, volumes, or domains. Install the Railway CLI, link your project with railway link, then run railway service source disconnect --service worker followed by railway service source connect --repo ZaRusb/telegram-npc-game --branch main --service worker. You can also update the source via the Public API.
Status changed to Awaiting User Response Railway • 22 days ago
15 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 15 days ago