a year 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.
18 Replies
a year ago
27908081-79e9-4395-9a7b-07b195477a36
a year ago
PR environments require the member role @Budi
a year ago
isn't that specifically what we added the deployer role for though?
a year ago
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.
a year ago
Which is what PR envs needs
a year ago
ahhhhh shows how much I don't know about PR environments haha
a year ago
It's a bit confusing, we can address that later. In the meantime, if moving to member helps unblock Budi- we're good.
a year ago
We can review workspace perms later.
a year 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?
a year ago
Strangely, I have another teammate who has a deployer role and his auto PRs work just fine.
a year ago
What's the difference between these two instances? I don't understand why one would fail and not the other.
a year ago
member is above deployer
a year ago
Deployer is only allowed to deploy, no logs or settings
a year 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.
a year 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.
a year ago
!s
a year ago
glad you figured out a solution that works for you!
a year ago
!s
Status changed to Solved brody • about 1 year ago