That blog post didn’t make a lot of sense to me. It’s saying to run CI in the merge queue. And also have CI be a script you can run locally. But also to replace CI?

Like:

> A merge queue is a script you run to push to origin/main (instead of using a PR UI like we did back in the GitHub, all-human days).

This really doesn’t capture what a merge queue is. It’s a queue of change sets to merge, and CI has to pass on each change set before it can merge. There’s still a CI process. You can’t really enforce that just by having a bash script agents run locally, you need something at a higher level to enforce it, which is… CI.

CI doesn’t have to be slow, and the author isn’t even arguing for removing the tests.