10 months ago
Hi Railway team!
I’m using Railway as a solo developer and I’d like to request a feature or some advice on how to achieve manual deployment approval for every deploy—even for my own commits as the repository owner.
Currently, Railway automatically deploys my own commits (since I’m the repo owner), but only asks for confirmation for commits from collaborators. However, sometimes I want every deployment to production to require manual approval, including deployments triggered by my own commits.
Why this matters:
There are times when I want to review the build before deploying to production, or just want an extra layer of safety to avoid accidental auto-deploys.
Questions:
1. Is there a way to force manual deployment approval for every commit, including my own?
2. If not, could you please consider adding this feature?
For example, an option to require manual deploy approval or to completely disable auto-deployment for a project/environment.
3. Is there any workaround available in the current Railway UI or API?
This feature would really help solo developers like myself maintain more control over production releases.
Thank you for considering this!
1 Replies
10 months ago
Hello!
1. There is not, sorry.
2. Please open a feedback post - https://station.railway.com/feedback with enough traction on your post we would definitely consider it.
3. You could always write the CI/CD pipeline yourself with a GitHub action and the railway CLI - https://blog.railway.com/p/github-actions
Best,
Brody
Status changed to Awaiting User Response Railway • 11 months ago
7 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 months ago
