Project ID: c61c1785-a8d8-43d0-9d8b-6bd1f69aa3bf

btw I had the same issue, I thought for some reason that deploying the latest commit was getting another branch's commit.

it should deploy the latest commit for your repo's default branch that you set in your repo's settings on GitHub

oh so i was right, any reason on why it doesnt get the default commit from the branch in the current service?

I don't know 🙂

Yeah it seems to point to the latest commit on Railway's Deployment History (at least for me). My current workaround is to reapply the Automatic Deploys, this triggers the first deploy, and then after it's deployed successfully you would switch off the Automatic Deploy but this triggers a second deploy it seems, so you end up doing 2 deploys when you really only want one.

I'd love to just have a button in the Sources section which just says "Deploy Latest Commit" (and have the commit link beneath it) instead of doing the quick links which I keep forgetting exist 😅

so why do you need to deploy the latest commit so often? feels like there is a deeper more important issue here?

Yes you're right, the deeper issue is that we have background jobs that tend to break/never resolve every time we have to deploy the specific service (the jobs can be up to 30 mins long) so the solution for now is to only deploy manually so we've got a bit more control

well what branch do you usually connect to your service, and what branch is default in github?

@cerwind - can you give this another try? I think we may have fixed it

Yeah works now 👍

awesome

!s