Can you provide more information on how you'd like to see this work? What usecase are you trying to solve?

@ngeloxyz, I'm employing Neon (PostgreSQL) with branching in my specific use case. A GitHub action automatically generates a corresponding Neon database branch when a new PR is created. The action returns a dynamic database URL particular to the new branch.

The challenge arises when I want to create a PR environment on Railway for this newly created PR. Given the dynamic nature of the database URL that changes with each new branch, I don't see a feasible way to accommodate this within Railway's PR environment feature in the UI. Its current design doesn't cater to this kind of variability in the database URL, which is necessary to my current workflow.

I hope this provides a good understanding of the use case that I am faced with.

Can you provide more information on how you'd like to see this work? What usecase are you trying to solve?

@angelo, I have the exact same problem.

I'm using Pierre instead of GitHub to deploy so would really like to be able to create new environments using the CLI

It's very useful since sometimes PR may be closed and re-open again, or opened before Railway configured, we can manually create PR environment for test and review.

And we need a feature is that we want to create PR environment on the PR from send from forked repo, currently we use GitHub Actions to auto create environments, however, CLI cannot create PR environment.

Does this achieve what you all are looking for?

https://docs.railway.com/guides/github-actions-pr-environment