Hey there! We've found the following might help you get unblocked faster:

• 🧵 I want to edit the deploy title with cli

• 📚 GitHub Actions PR Environment

• 🧵 Receiving 403 in github actions CLI - randomly stopped work?

If you find the answer from one of these, please let us know by solving the thread!

Hi there! It looks like the CLI can differentiate between environments. For example, the railway link command (see: https://docs.railway.com/reference/cli-api#link) supports an --environment flag:

You can also use the interactive command to switch between environments: railway environment

I came across this thread where someone ran: railway up -e production but it sill got deployed to staging. Turns out that if you’re using RAILWAY_TOKEN in CI/CD, that token is bound to a specific environment when created, which overrides the -e flag—just something to watch out for.

From what I can tell (and anyone can confirm/deny), Railway doesn't directly work with branches - instead it uses environments, and you configure which GitHub branch gets triggered for each environment. From the Github auto deploy docs:

"Services that are linked to a Github repo automatically deploy when new commits are detected in the connected branch."

Their docs on environments are here. I’m planning to test this myself later this week to confirm, but based on the docs, this should help you get started! Feel free to me know if you run into any issues!

Yeahhh this worked! Had to make a new environment on the railway dashboard, named it testing.

Then I used railway link --environment testing  for testing branch which builds from testing branch of the repo and railway link --environment production for the same repo that builds from main branch.

So doing railway up from the different branches is building for the environment it needs. Thanks so much!