Long story short, we are tightening the ability for people who deployed a repo on Railway into their project to prevent upstream repos force deploying into a user's environment without their knowledge.

Are you added as a member of their team?

n/a

Yes, my permission is "Can Edit"

Does this mean that every Git Push needs to be explicitly deployed in Railway now?

Also from what I can tell nothing has been pushed to this repo for a year.
Yeah last commit 10 months ago

You not being part of their Pro team is what is preventing the pushes from auto deploying, so they would need to manually approve any pushes.

This is done so people can't push code into someone elses project without the owner knowing.

We also have new docs on the way to explain this, and I will update you when those land!

!team

!t

Tracking this, for what it's worth, we don't want to be impacting anyone's consulting business so would love to grab requirements.

@Andy - if you don't mind me asking, what is usually the consulting arrangement, do you pass the project to a team and add yourself as a project member?

It was a while ago, but I think I set it up on my account first and transfered ownership? I don't know if that's a thing. If not, then I deleted the version on my acct and had them set it up on their account and add me

Is the repo under your GitHub?

It is a private GitHub repo owned by an "organization"
I and the client are members are both "owner" of the organization on GitHub

Gotcha- lemme take it back to the lab to try to smooth it out. But I owe you and other users docs first.

Hello, jumping here because I have questions regarding this
If it's better to create a new thread let me know 🙂

@Brody is there a way to by pass this approval step as it was before?
Because if we have 10 developers pushing to a branch which is linked to railway, it means I need to add the 10 of them as team member of the pro plan to enable them to auto deploy is that correct?

!t

Yes, you will need to add them to the pro plan.

Whats your usecase, are you a agency?

mmmh that's troublesome tbh… is there any alternative?
this will change significantly our monthtly cost

We are not an agency, just a startup

Curious question here, what makes the $20 per seat cost not worth it to your company?

every single dollar we can save we save it.. startup life sir

so what's my alternatives? I was not aware of this change that impact our monthly cost (20$ is ok, but that's for one seat, if I need to add 10 more people that's 200$ more per month)

From our point of view, Railway, unlike other providers- doesn’t charge for build hours or CIs or a per service premium cost on usage like other PaaS. We feel the seat cost helps align incentives.

You get near unlimited builds for just $20 per person who needs it. $200 in our mind is drastically cheaper than hiring a DevOps person and hopefully we save you the time to boot.

Although this feature was never intended to be DRM, Railway was never intended to be used with a shared account, one seat == one contributor.

@angelo can we continue this discussion privately? Wanna ask few more stuff

Hey, I'm not Angelo but yes absolutely! you can open a private thread on our help station -

Your message was very late for Angelo's timezone but he will see your private help station thread!

I am the only dev pushing my application and I need to approve myself???

nothing. I get this error Must have access to the repository to approve deployments.

Does the GH on your account match with the GH for the repo?

pretty much.

i have my normal account and my org account. my companies apps are in my org account.

Is the repo under the org account?

yes it is

(Sorry for questioning, your problem is real, just wanna model it so that we are shipping fixes we get to yours.)

after I select the org, nothing happens. it takes me back to railway and it still says connect to org

Anybody looking into this? as I have a business to run.

You sent that message at 4am, the team is generally based in EST. The first message you sent was at 4pm, close to the end of the work day

be patient. On the hobby plan you are not guaranteed a response within an SLA time. There is a reason the pro plan exists

Okay