Commit Queue about automation HOT 8 CLOSED

Until we have a consistently green and consistently functioning CI, this is going to be dang near impossible to do. There is too much in the landing process that requires manual intervention, not the least of which is interpreting CI results.

from automation.

@jasnell it could be kicked off only at the point you would manually do it yourself. That would remove the potential for error when landing the commit

from automation.

The Rust project has a https://github.com/bors IIUC it pretty much does the same kind of stuff, but on Github. Pick a merged PR to see what it does.

from automation.

Refs: nodejs/build#705
There's seems to be prior art, I'll try to find references.

from automation.

Until we have a consistently green and consistently functioning CI, this is going to be dang near impossible to do.

It's not a big deal in practice. Rust doesn't have that either, getting something landed sometimes takes a few retries, but it's okay because it's automated.

I for one would be very pleased if this went through.

from automation.

;) Ok... So long as it is focused on the after CI bits, I'm +1. Eventually we need to take a serious look at CI tho

from automation.

If anything the commit queue increases the incentive to fix flakiness.

from automation.

Some thoughts on the next step of node-core-utils: https://github.com/joyeecheung/node-core-utils/issues/10 , could potentially be used by the bot, right now the goal is "good enough for human to use".

from automation.