Committing changed settings are skipped
When updating variables or settings and committing these changes with the new UI, the builds are skipped when the last commit has no changes in the watch patterns. One would expect that a build triggered by updating variables or settings are always executed and not skipped.
8 Replies
Project ID:
3160979a-66a1-4ab0-b77f-1ef3fe72acf43160979a-66a1-4ab0-b77f-1ef3fe72acf4
You are exactly right! I'll create a ticket to fix
Any chance on an ETA on this?
Thread has been flagged to Railway team by @Adam.
Hey, sorry not yet - we're currently busy with meetings planning what our quarter looks like, but we'll circle back very soon. Thank you for the patience!
@jr do you have a Linear tix for this I can attach to the thread?
https://linear.app/railway/issue/PRO-1660/do-not-skip-deploys-created-for-staged-changes
This should be live soon 🙂
Awesome