The "Deploy latest commit" command is very useful for manually triggering deployments. Our process currently uses this as a human-in-the-loop step for releasing to our highest environment.

It would be helpful to have a slightly tweaked version of this command "Deploy from commit [SHA]" which enables deploying the service from a specific commit in the linked Github repo. This would enable deploying commits that sit on a main branch's non-HEAD that were never previously deployed in a given environment.

Example:

Staging environment -> auto-deploys on commits to main

Prod -> only on manual

At time t -> staging has commit 3, prod has 2; in the past staging had deployments of commits 1 and 2, prod has never had commit 1.

At time t+1 -> new commit 4 to main branch triggers deployment in staging env. Staging moves to commit 4. Prod stays on commit 2.

At time t+2 -> decision "we're going to move prod to commit 3" -> not currently possible because latest commit on main is commit 4 and it's not possible to "redeploy" a previous build in prod because commit 3 has never been built in prod.

---

There are obviously non-Railway solutions here, like having a dedicated prod branch. The extra command would be helpful though.