Bug with PR Environments when reconnecting Github repository
We recently had to reconnect our Github repository due to the Github repo's organisation name changing. We noticed we had to reconnect because there seemed to be no deployment activity on Railway on any of our branches.
When we went to Project > Settings > Environment and clicked "Connect Environment to Branch", an error popped up "[org/repo] not found. Are you sure the repo exists and you have access to it?"
We reconnected the Railway to our Repo, and all our PR Environments reconnected to the
main branch, not their respective PR branch. We had to go through each PR branch and select the correct branch to connect to.
Project ID: 3c08e827-8d73-4a37-bbe9-9af9757bd3542 Replies
Project ID:
3c08e827-8d73-4a37-bbe9-9af9757bd354Just a follow-on, we're not stuck or waiting on anything, we remedied this by pointing each PR Environment to the respective branch. Just wanted to let you know.