Skip to content
Workspace member auto-deploys not working

2 years ago

I'm on a Pro plan. My colleague is a Workspace member with Deployer role. Whenever he creates a PR for one of the repositories linked to a project in our Workspace in Railway, he gets this error regarding autodeploys:

This PR was not deployed automatically as @d3cie does not have access to the Railway project.

In order to get automatic PR deploys, please add @d3cie to your team on Railway.

How can we fix this? Thx.

Solved

18 Replies

2 years ago

27908081-79e9-4395-9a7b-07b195477a36


PR environments require the member role @Budi


2 years ago

isn't that specifically what we added the deployer role for though?


Deployer will waive the deploy through once merged to main but it doesn't grant us perms to spin up a new set of CI on your behalf.


Which is what PR envs needs


2 years ago

ahhhhh shows how much I don't know about PR environments haha


It's a bit confusing, we can address that later. In the meantime, if moving to member helps unblock Budi- we're good.


We can review workspace perms later.


2 years ago

Confirming the downgrade needs to happen on the workspace and not the project level? So I need to downgrade the user from deployer to member?


2 years ago

Strangely, I have another teammate who has a deployer role and his auto PRs work just fine.


2 years ago

What's the difference between these two instances? I don't understand why one would fail and not the other.


member is above deployer


Deployer is only allowed to deploy, no logs or settings


2 years ago

We were strangely able to figure this out by keeping the user a Deployer on the workspace, but also inviting them as a Member on the project.


2 years ago

I'm not sure if this is the intended behaviour, but I can say that as a user it's not been intuitive for me.


2 years ago

!s


2 years ago

glad you figured out a solution that works for you!


2 years ago

!s


Status changed to Solved brody • over 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...