Repo transfers on GitHub change the underlying repository identifiers, which can break the webhook linkage even though the UI still shows it as connected. To fix this, go to your service's Settings, disconnect the repo entirely, then reconnect it by selecting the new clear-go-to-market/Clear-Platform repo and the correct branch - this will re-establish the webhook so pushes trigger deployments again.

Making changes (even ones like redeploying the exact same repo name, not a change) have at times allowed Railway to pick up and deploy some things sitting on main, but I still haven't been able to get it to reliably do what it's supposed to do.

• Latest deployed commit: 16fd687923a6fa5e6847a1db5197064b4eefa2d9
• Backed-up commits on main still not being picked up

I moved everything back to the original repo name and back to an individual account and it's working for now. However, I would like to move it to an or so would still appreciate support here.

When you transfer the repo to the organization again, the webhook linkage will break because the underlying GitHub repository ID changes. Right after the transfer, go to each affected service's Settings, disconnect the repo under Source Repo, then reconnect it by selecting the new org repo (e.g. clear-go-to-market/Clear-Platform) and branch. This re-registers the webhook at the service level, which is different from the account-level GitHub integration you previously reconnected. Also confirm under GitHub Settings -> Applications -> Railway App -> Configure that "Repository access" includes repos in the clear-go-to-market org.

(This is due to the GH API not re-registering, might be something we have to fix on our end.)

Is this something you can assist with then? I really do want to move this to an organization. Repo name change isn't critical.

Hey — yeah we can help with this. The disconnect/reconnect at the service level should work after you transfer to the org. The key thing is doing it in this order: transfer the repo to the org first, then in Railway go to each service's Settings → disconnect the repo → reconnect it by picking the new org repo. That re-registers the webhook at the service level which is what's broken after a transfer. Make sure the Railway GitHub App is installed on the clear-go-to-market org with access to the repo too. If you hit any issues during the process ping us here and we can take a look in real time.

Hi — following up on the GitHub-pushes-not-triggering-deployments issue after a repo transfer. I tried once again to get this to work, because I'm trying to connect with a SOC 2 facilitator who can't connect with a personal repo.

▎ Summary: I transferred bjensen1981/b2b-ai-interviewer

▎ (personal) into our org as

▎ clear-go-to-market/b2b-ai-interviewer. After the transfer,

▎ the production service's source binding broke and never

▎ recovered. I worked through every documented step:

▎

▎ 1. Confirmed the Railway GitHub App was installed on the

▎ clear-go-to-market org (installation 119208308) with All

▎ repositories access.

▎ 2. On the production service (project

▎ bd74ef2d-70b6-4747-a4cd-e4850ee3001a, service "Clear"):

▎ disconnected the source, deployed, reconnected to the org

▎ repo on main, and deployed again.

▎ 3. Did a full uninstall + clean reinstall of the Railway

▎ GitHub App on the org.

▎ 4. Re-authorized my GitHub account connection in Railway.

▎

▎ Throughout, "Branch connected to production" kept

▎ alternating between "GitHub Repo not found" and "Bad

▎ credentials" and never went green. The service stayed

▎ Online and served traffic fine — only the GitHub source

▎ binding / auto-deploy was broken. This looks like the

▎ GH-API-not-re-registering-after-transfer issue mentioned

▎ in the thread; I suspect a stale installation reference on

▎ your side (possibly still pointing at my old

▎ personal-account installation 119215796 rather than the

▎ org installation 119208308).

▎

▎ What I've done as a temporary fix: I've moved the repo

▎ back to my personal account

▎ (bjensen1981/b2b-ai-interviewer) and reconnected the

▎ Railway services there to restore push-to-deploy.

▎

▎ REQUEST: This repo needs to live in

▎ the clear-go-to-market org long-term. Given the

▎ auto-rebind didn't work twice, can we redo the org

▎ transfer together, live, so you can re-point / re-register

▎ the source binding on your end the moment I transfer?

▎ There are two services in the project that need it —

▎ production and staging.

Happy to look into this further, just confirming you reconnected after the transfer as in angelo's steps?

Yes, followed their steps exactly, numerous times.

Please:

• Disconnect
• Remove the GitHub account
• Move the project
• Re-add the GitHub account (installation)
• Readd the trigger