mergeloop
MergeLoop
Pull requests in this repo land through MergeLoop's merge queue. Queue a PR with a label and let MergeLoop merge it; merging by hand or pushing to the default branch races the queue.
The labels
The trigger label is label in .mergeloop/mergeloop.yml on the default branch, mergeloop when the file leaves it out. A repo set up before MergeLoop was renamed may still have its file at .mergepatrol/mergepatrol.yml, where the label left out is mergepatrol. Below, <label> stands for it, and "the config file" for the file.
<label>queues the PR:gh pr edit <number> --add-label <label>. Removing it leaves the queue, and cancels the PR's run.<label>:priority, beside<label>, puts the PR at the front of the queue.<label>:failedis set by MergeLoop when it ejects the PR.
Over MCP
When the mergeloop MCP server is connected (an older connection may be named mergepatrol), use its tools instead of the labels: queue_pull (with priority for the front of the queue), dequeue_pull, pull_status and list_queue. They change the same labels, as the GitHub user or bot the server was connected as, so everything below still holds. pull_status reads where a PR is without parsing MergeLoop's comment. The server's other tools read the queue, the agent's review and the queue's history, and change a repo's MergeLoop settings. Reviews, approvals and comments happen on GitHub, with gh.
With the mergeloop command
Land a PR with the mergeloop command instead of the steps below. If it is not on the PATH, install it, for macOS or Linux: