2 years ago
Hi everyone,
Today, I noticed that when I push a new update to the main branch of my connected repository, it does not trigger a new deployment in Railway. Railway doesn't seem to recognize that the repository has been changed, so there's no way to manually trigger a deployment as well.
I have confirmed that the repository is connected and the correct branch (main) is selected under "Branches connected to production."
I was able to trigger a deployment by unlinking and then re-linking the branch, but future pushes to the branch do not trigger a deployment.
3 Replies
2 years ago
there's no way to manually trigger a deployment as well.
Yes there is! ctrl / cmd + k -> deploy latest commit
Was this service originally deployed from a template?
2 years ago
That worked for me! And it looks like automatically deploying when a commit is made is back now. Thank you :)
I'm unfortunately not sure how to tell if it was deployed from a template, but it was a Python-Flask app built with Nixpacks.
2 years ago
All is good then.
The was this deployed from a template question is answered simply by answering if you deployed it from a template lol.
Status changed to Solved brody • over 1 year ago