Renaming a GitHub repo can break the webhook connection that triggers PR environment creation. To fix this, go to each affected service's settings, disconnect the repository source, then reconnect it to the renamed repo. You should also confirm the Railway GitHub App has access to the renamed repository in your GitHub installation settings.

We have done two cycles of disconnecting and reconnecting services and even completely uninstalled and reinstalled the Railway GitHub app, and that has not solved the problem.

Good news, this isn't the repo rename. Your PRs all target main, but no service in this project deploys from main right now (they're on qa, production/*, demo/*, and a few feature branches). PR environments only get created when at least one service in the project is set to deploy from the branch the PR is opened against, so every PR since #91 was skipped.

To fix it, set one service's deploy branch to main. The PR environment will still fork from qa, since that's your base environment. One thing to know: that service will then also deploy automatically on pushes to main, so pick one where that's fine.

We agree this should be much more obvious in the UI.