Replace your CI with a merge queue
Blog post from exe.dev
Continuous Integration (CI) has traditionally involved running tests in the cloud after code commits are merged to ensure code quality, but this approach faces challenges with the increasing use of automated agents in development. While human engineers benefit from CI by leveraging their understanding of a codebase, agents lack this implicit knowledge, leading to frequent regressions and inefficiencies. To address these issues, it is suggested to replace CI with a merge queue system, which allows all tests to be run before code is integrated into the main branch. This ensures that agents can identify and resolve issues in real-time, preventing broken builds and enhancing efficiency. In the era of agents, fast testing becomes crucial, making the merge queue a superior solution despite the need for more robust computing resources to support this approach.