N/A

The most effective way to achieve this would be to commit to another branch instead of main, then PR to main when you believe your code is actually ready to deploy.

well, we kinda already have the dev branch, but it would be better if there was a way to not make it restart every commit :P

anyways, thanks for the reply.

The only way that's possible right now is by removing the source repo from the service, then using the CLI to update the service instead of relying on automatic deployments

hm

Perhaps you may want a staging branch. This would be the step between dev and production.

How may I set up that?

Create a new branch in your git repo, then point railway to that branch in the service settings

When you want to update what railway sees, merge dev branch into the new staging branch

^ that’s exactly what I suggested up here

one step removed, though

I suggested dev -> main, if you find benefits in dev -> staging-> main, you might find pull request environments useful

https://docs.railway.com/guides/environments#enable-pr-environments

!s