node icon indicating copy to clipboard operation
node copied to clipboard

tools: add a backport queue cron action

Open aduh95 opened this issue 2 months ago • 2 comments

This should help the Release team to keep up with backports, by getting notified sooner when there's a backport conflict.

I've tried compiling and running tests as part of the workflow but it's not reliable and would force us to limit the number of commits to avoid timeouts.

I'm using a different branch, I don't think we want the automation to push to the staging branches because:

  • It's only able to work with commits that cleanly apply to the staging branch, which is trivial for a human to do.
  • No matter how small of a conflict, as soon as a commit doesn't backport it is skipped, and having out of order backports makes branches diverge more and more, making future backport harder.
  • Releasers sign their backport commits. Because commits that land on staging branch receive much fewer attention than the one on main, we don't want anyone to be tempted to introduce subtle backdoor when backporting, having the signature puts the releaser reputation at stake. I don't think we could have the same system with a bot while making sure no one can impersonate the bot.

aduh95 avatar Dec 05 '24 11:12 aduh95