a year ago
I use Railway's PR Environments with Github integration. It seems that only PRs opened by members of my Railway project can benefit from this feature as I have this message on Github:
This PR was not deployed automatically as "..." does not have access to the Railway project.
In order to get automatic PR deploys, please add "..." to your team on Railway.
----
I don't want to invite all the developers in my team, as most of them have no reason to be on Railway and don't deal with infrastructure issues. It's both unnecessary logistics and a safety issue.
We are in the process of migrating from Render, which works without requiring members to be added. Is it possible to do this on Railway?
4 Replies
a year ago
On our platform, they would have to be Deployers at least to allow for automatic deployments the way Railway intends.
Status changed to Awaiting User Response Railway • 12 months ago
Status changed to Solved parmstar • 12 months ago
Status changed to Awaiting Railway Response fadri1 • 12 months ago
parmstar
On our platform, they would have to be Deployers at least to allow for automatic deployments the way Railway intends.
a year ago
What is "Deployers"?
Do you confirm that for a PR opened by a junior front-end developer creating a preview environment, it is necessary that this developer also has the necessary rights to modify our production environment?
If so, this makes no sense and does not meet corporate security standards. Do you plan to give more control over this feature in the future?
a year ago
I've discovered that “Deployers” are members of the workspace (i.e. paying members) and not members of the project (free).
Anyway, if it can help someone I've found a solution: closing the PR and reopening it with 2 clicks in Github does the trick.
a year ago
https://docs.railway.com/reference/teams#inviting-members
You can see what Deployer entails there as a role.
Status changed to Awaiting User Response Railway • 12 months ago
Status changed to Solved parmstar • 12 months ago