a month ago
I want to change the managed environments feature to only spin up selected PRs, not every PR. I know this has been discussed here: https://station.railway.com/feedback/is-there-a-way-to-create-pr-environments-76f19cd4
However, the answer is a bit poor. If Railway CLI is already being used by you guys to spin up the managed PR environments why can't we also use it selectively? I don't understand why this is difficult.
What I want is:
- no managed PR environments spun up, by default
- a way to use the CLI to spin up a managed environment just for a specific PR and tear it down when the PR is merged.
3 Replies
a month ago
PR environments are currently all-or-nothing: when enabled, every opened PR creates one, and there's no built-in filter to limit which PRs trigger them. The "Focused PR Environments" option controls which services deploy inside a PR environment (for monorepos), but not which PRs get environments. The CLI's railway environment new creates a regular persistent environment, not an ephemeral one tied to a specific PR's lifecycle, so it wouldn't auto-tear-down on merge. This selective-PR-environment workflow isn't something we support today.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
PR environments are currently all-or-nothing: when enabled, every opened PR creates one, and there's no built-in filter to limit which PRs trigger them. The "Focused PR Environments" option controls which *services* deploy inside a PR environment (for monorepos), but not which PRs get environments. The CLI's `railway environment new` creates a regular persistent environment, not an ephemeral one tied to a specific PR's lifecycle, so it wouldn't auto-tear-down on merge. This selective-PR-environment workflow isn't something we support today.
a month ago
But that doesn't mean I don't really want this. The "all-or-nothing" approach is overwhelming me. We might get 15 PR's every couple hours... then the environment dropdown is huge. Plus some PR's sit around for weeks, leaving those environments grinding away cash. It sucks.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
You're right that PR environments are all-or-nothing today, and we understand the cost and clutter pain at that PR volume. There's no built-in way to selectively trigger them, and the CLI's environment new creates persistent environments rather than ephemeral PR-linked ones, so it's not a drop-in workaround. The feedback thread you linked is the right place to push for this, and upvotes there directly influence prioritization.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago