Disable external-contributor deploy approval for our workspac

sistemas-envio-tech

PROOP

a day ago

Hi! Our team has many GitHub collaborators who merge PRs into our deploy

branch (developer), so every merge commit is flagged as an "external

contributor" and our deployments sit in "Needs approval" pending manual

approval every time.

We'd like to skip this approval step for our workspace.

Workspace: sistemas-envio-tech

Service: work-manager (project work-dev)

Repo: sistemas-envio-tech/work-manager

Could you please whitelist our workspace to disable the external-contributor

deploy approval, like in this thread?

https://station.railway.com/questions/auto-deployment-for-external-contributor-dedcd613

Thanks!

Awaiting User Response

3 Replies

Status changed to Awaiting Railway Response Railway • 1 day ago

brody

EMPLOYEE

a day ago

I'm sorry, but we can no longer offer that. Removing features would be limited to enterprise.

Please add the developers to either the workspace or the project.

Status changed to Awaiting User Response Railway • 1 day ago

brody

I'm sorry, but we can no longer offer that. Removing features would be limited to enterprise. Please add the developers to either the workspace or the project.

sistemas-envio-tech

PROOP

15 hours ago

Thanks Brody! Before I add everyone, just want to confirm a couple of things:

Is adding the developers as "viewer" to just the PROJECT (work-dev) enough

for their merge commits to auto-deploy without the "Needs approval" prompt,

or do they need to be added to the whole workspace?
For the matching to work, does each developer need to have their GitHub

account connected to their Railway account? Or is being invited to the

project enough on its own?
Does each viewer/member count as a billable seat on our Pro plan? We have

~6 collaborators who merge PRs into our deploy branch (developer).

Thanks!

Status changed to Awaiting Railway Response Railway • about 15 hours ago

brody

EMPLOYEE

an hour ago

Yes, that is enough; the permissions level is inconsequential.
They need to each have GitHub linked to their Railway accounts.
There is no such thing as a billable seat. We have not charged for seats, regardless of permission levels, for over a year.

Status changed to Awaiting User Response Railway • about 1 hour ago

Welcome!