Form cover
Page 1 of 1

PR Environments

A big focus for us this quarter is improving the experience around PR environments, and we'd love to know your experience today.
Your feedback will go directly into improving this feature.

Do you use PR environments on Railway?

When a PR contains a net new service to be added, or net new configuration, like a new variable, when do you add those to your Railway project? Before or after you merge the PR?

For example, in your code, you add support for caching with Redis. This requires a new Redis service on Railway AND a new REDIS_URL variable. What is your current flow like, for incorporating a change like this?

What information would you like to see in the GitHub comment that Railway leaves on a PR?

This assumes you use PR environments in Railway. Put N/A if you do not use them.
Click here to see an example of what happens today.

Would you like to see a failed status check if you add a variable to a PR environment without also adding it to your production environment?

General Questions

Where do Railway environments currently fall short in your workflow?

Have you synced changes between environments before? How was your experience?

Anything you would like to see with Railway environments, that we haven't captured here?