8 days ago
Connected to Github. Don't want to deploy for every new commit. Turned off auto-deploy.
But now there's no way for me to manually trigger the deployment easily. Turning on auto-deploy AFTER the target commit was pushed to the target branch is a no-op: the auto-deploy doesn't detect that the target branch has moved. I can disconnect and re-connect the branch and that works, but that automatically enables auto-deploy, which has (more than once) lead to me forgetting to disconnect the branch again or turn off auto-deploy.
The simplest solution that I think should be implemented: when the branch is connected from Github, add a button to the side to trigger a commit comparison. If the commit in that branch in Github matches the current deployment, it's a no-op. If it doesn't match, deploy the commit from Github,
Is there a solution that currently works that I haven't seen somewhere?
2 Replies
8 days ago
With auto-deploy disabled, you can open the Command Palette (CMD/CTRL + K) and select "Deploy Latest Commit" to deploy the latest commit from your connected branch on demand, no need to toggle auto-deploy or reconnect.
Status changed to Awaiting User Response Railway • 8 days ago
Railway
With auto-deploy disabled, you can open the Command Palette (`CMD/CTRL + K`) and select "Deploy Latest Commit" to deploy the latest commit from your connected branch on demand, no need to toggle auto-deploy or reconnect.
8 days ago
oh perfect, that is exactly what i wanted.
somehow i didn't realize there was a command palette for each individual service.
also, maybe it would be helpful to also have that "Deploy Latest Commit" button in the settings page as well. right now it seems a bit obscure.
Status changed to Awaiting Railway Response Railway • 8 days ago
Status changed to Solved justyouand • 8 days ago