> Otherwise we will trigger it on the change the schedule originally triggered on.
I think this is the only real departure from the existing behaviour, wherein if we can’t find a changelist of at least X - we just abandon the schedule. You may want to consider maintaining that behaviour unless there’s a specific reason.
Otherwise, I think this makes sense to me. Once you’ve got a change, going feel free to share it back here or consider forming a PR, as it could be something the team may want to integrate back as a first class feature (I can certainly think of at least the N gate requirement being something they’d review).
Let me know if you need a hand with anything.
Kind regards, and good luck!
Julian