a month ago
I build small internal tools for small businesses and hand each project over so the client owns it in their own workspace. Two things I can't find an answer to:
Autodeploys need a project member with a connected GitHub account that has access to the repo. After transfer the owner is the client, who has no GitHub account. If they keep me in the workspace as a Deployer, does my connected GitHub account satisfy that, so a push from me still deploys? And can a Deployer see logs? The docs and an older thread differ.
On transfer, staff have confirmed volumes, variables, deployment history, services and the up.railway.app domain carry across. Do custom domains and the GitHub repo connection carry across too, or does the new owner need to do anything after accepting?
Thanks
Pinned Solution
a month ago
Yes, Deployer is enough for GitHub autodeploys. Railway’s current permissions table explicitly allows automatic GitHub deployments for Deployers, but they can’t view logs or change service settings/variables. So keeping yourself in the workspace as Deployer with your GitHub account connected should cover the deployment part. I’d still do one test push after the ownership transfer just to confirm the repo integration stayed intact..
3 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
After transfer the owner is the client, who has no GitHub account.
This is a bit confusing, can he not make a free GitHub account?
I am pretty sure it just needs your credentials to get the information from GitHub. But if you are a deployer that should work. The simplest solution is probably to create a free GitHub organization under a "transfer" account set it all up for them and then hand them the login to the transfer account on GitHub which will give them the organization, source code and control over deployments
a month ago
Yes, Deployer is enough for GitHub autodeploys. Railway’s current permissions table explicitly allows automatic GitHub deployments for Deployers, but they can’t view logs or change service settings/variables. So keeping yourself in the workspace as Deployer with your GitHub account connected should cover the deployment part. I’d still do one test push after the ownership transfer just to confirm the repo integration stayed intact..
mastter-nsk
Yes, Deployer is enough for GitHub autodeploys. Railway’s current permissions table explicitly allows automatic GitHub deployments for Deployers, but they can’t view logs or change service settings/variables. So keeping yourself in the workspace as Deployer with your GitHub account connected should cover the deployment part. I’d still do one test push after the ownership transfer just to confirm the repo integration stayed intact..
a month ago
Great, thanks for your help!
Status changed to Solved dev • about 1 month ago