Unable to connect service to a repo
I am deploying a service from scratch via an empty project through a source repo. The source repo is correctly identified but when I try to select a branch under Automatic Deployments in the Git Repository Section I encounter an endless spinner of "Connect Environment to Branch" after an error
"Error: Creating service trigger
Only a single deployment trigger is allowed per (environment, service) pair"
I was wondering how to remedy this?
Solution:Jump to solution
Nvm solved, turns out the github app was suspended on the team but if Github can surface a better error (and relay it to railway) then would prevent issue of trying to find out if Railway is the root cause or elsewhere
17 Replies
Project ID:
7b1d4989-a0d3-4bb1-98de-a5372becb82d7b1d4989-a0d3-4bb1-98de-a5372becb82d
When checking via graphql the deployment triggers it looks like it is currently set on the dev branch but I want to change the branch
remove the repo and re-add it?
By doing this?
yeah
Hmm now getting this
(I did not change any permissions in this process)
I am using a private repo but within an org that does have access (both myself/team)
well thats not ideal
@Ray any idea?
any way to check what repos can be accessed per team? to doublecheck and ensure it's there?
Solution
Nvm solved, turns out the github app was suspended on the team but if Github can surface a better error (and relay it to railway) then would prevent issue of trying to find out if Railway is the root cause or elsewhere
i dont have a clue, sorry
No worries 🙂
ah glad you solved
maybe a suggestion would be to refresh on some interval or after a failure to remove the list of available repos from the list (because despite the app being suspended the repo was still a selectable option within railway)
which can lead to the confusion of "well I see it in the list to choose from I must have permissions"
good feedback!