From c271487a588d8ced8069a639dc053f0198dc14d4 Mon Sep 17 00:00:00 2001
From: "merge-patrol[bot]"
 <349684721+merge-patrol[bot]@users.noreply.github.com>
Date: Thu, 29 Oct 2026 15:24:12 +0000
Subject: [PATCH] Set up Mergepatrol

---
 .agents/skills/mergepatrol/SKILL.md | 38 +++++++++++++++++++++++++++++
 .claude/skills/mergepatrol/SKILL.md | 38 +++++++++++++++++++++++++++++
 .mergepatrol/mergepatrol.yml        | 12 +++++++++
 3 files changed, 88 insertions(+)
 create mode 100644 .agents/skills/mergepatrol/SKILL.md
 create mode 100644 .claude/skills/mergepatrol/SKILL.md
 create mode 100644 .mergepatrol/mergepatrol.yml

diff --git a/.agents/skills/mergepatrol/SKILL.md b/.agents/skills/mergepatrol/SKILL.md
new file mode 100644
index 0000000..d7e48a2
--- /dev/null
+++ b/.agents/skills/mergepatrol/SKILL.md
@@ -0,0 +1,38 @@
+---
+name: mergepatrol
+description: This repo merges pull requests through Mergepatrol, a label-driven merge queue. Use when merging, landing or shipping a PR, queueing or dequeueing one, or reading a Mergepatrol comment or label on a PR.
+---
+
+# Mergepatrol
+
+Pull requests in this repo land through Mergepatrol's merge queue. Queue a PR with a label and let Mergepatrol merge it; merging by hand or pushing to the default branch races the queue.
+
+## The labels
+
+The trigger label is `label` in `.mergepatrol/mergepatrol.yml` on the default branch, `mergepatrol` when the file leaves it out. Below, `<label>` stands for it.
+
+- `<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>:failed` is set by Mergepatrol when it ejects the PR.
+
+## What the queue does
+
+Mergepatrol rebases the PR onto the default branch, and may test it in a batch with other queued PRs. It resolves conflicts with an agent, runs the repo's `verify` commands, waits for the required checks, then merges with the repo's default merge method. When a required check fails, an agent commits a fix to the PR branch and the checks run again, a few times at most, unless `fix_ci` turns it off. The queue only serves PRs that target the default branch, and stacks of PRs (from `gh stack`) that merge into it.
+
+A PR from a fork merges only as it was when the label went on: a push to it after that takes it out of the queue, until a maintainer adds `<label>` again. It never joins a batch, gets no agent, and is ejected on a conflict or a failed check. Mergepatrol can push its rebase only while the author allows edits by maintainers.
+
+A stack is one item of the queue. The label on any of its PRs queues the whole stack, and the stack waits until every PR in it is ready. Mergepatrol rebases every layer when the stack is behind, and merges the stack all at once: every PR, or none. When it ejects a stack, every PR in it gets `<label>:failed`.
+
+The rebase rewrites the PR branch, and a fix adds a commit to it. Before pushing more commits to a queued PR, fetch it and rebase your work onto the remote branch. A push to a queued PR makes Mergepatrol start the PR over.
+
+## Reading its status
+
+Mergepatrol keeps one comment on each queued PR up to date. It says one of:
+
+- **On hold**: the PR is a draft, waits for a required review, or has changes requested. Mergepatrol comments the reason on the PR. It keeps its place, and runs once GitHub shows it ready.
+- **Ejected**: the rebase, the checks or the merge failed, and the comment says which. The trigger label is gone and `<label>:failed` is on. Fix the cause, push, then add `<label>` again.
+- **Merged**: done. The queue labels are removed.
+
+## Settings
+
+`.mergepatrol/mergepatrol.yml` sets the label, the batch size, the conflict resolver, the `verify` commands, and `fix_ci`. Mergepatrol reads it from the default branch, so a change takes effect once its PR merges.
diff --git a/.claude/skills/mergepatrol/SKILL.md b/.claude/skills/mergepatrol/SKILL.md
new file mode 100644
index 0000000..d7e48a2
--- /dev/null
+++ b/.claude/skills/mergepatrol/SKILL.md
@@ -0,0 +1,38 @@
+---
+name: mergepatrol
+description: This repo merges pull requests through Mergepatrol, a label-driven merge queue. Use when merging, landing or shipping a PR, queueing or dequeueing one, or reading a Mergepatrol comment or label on a PR.
+---
+
+# Mergepatrol
+
+Pull requests in this repo land through Mergepatrol's merge queue. Queue a PR with a label and let Mergepatrol merge it; merging by hand or pushing to the default branch races the queue.
+
+## The labels
+
+The trigger label is `label` in `.mergepatrol/mergepatrol.yml` on the default branch, `mergepatrol` when the file leaves it out. Below, `<label>` stands for it.
+
+- `<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>:failed` is set by Mergepatrol when it ejects the PR.
+
+## What the queue does
+
+Mergepatrol rebases the PR onto the default branch, and may test it in a batch with other queued PRs. It resolves conflicts with an agent, runs the repo's `verify` commands, waits for the required checks, then merges with the repo's default merge method. When a required check fails, an agent commits a fix to the PR branch and the checks run again, a few times at most, unless `fix_ci` turns it off. The queue only serves PRs that target the default branch, and stacks of PRs (from `gh stack`) that merge into it.
+
+A PR from a fork merges only as it was when the label went on: a push to it after that takes it out of the queue, until a maintainer adds `<label>` again. It never joins a batch, gets no agent, and is ejected on a conflict or a failed check. Mergepatrol can push its rebase only while the author allows edits by maintainers.
+
+A stack is one item of the queue. The label on any of its PRs queues the whole stack, and the stack waits until every PR in it is ready. Mergepatrol rebases every layer when the stack is behind, and merges the stack all at once: every PR, or none. When it ejects a stack, every PR in it gets `<label>:failed`.
+
+The rebase rewrites the PR branch, and a fix adds a commit to it. Before pushing more commits to a queued PR, fetch it and rebase your work onto the remote branch. A push to a queued PR makes Mergepatrol start the PR over.
+
+## Reading its status
+
+Mergepatrol keeps one comment on each queued PR up to date. It says one of:
+
+- **On hold**: the PR is a draft, waits for a required review, or has changes requested. Mergepatrol comments the reason on the PR. It keeps its place, and runs once GitHub shows it ready.
+- **Ejected**: the rebase, the checks or the merge failed, and the comment says which. The trigger label is gone and `<label>:failed` is on. Fix the cause, push, then add `<label>` again.
+- **Merged**: done. The queue labels are removed.
+
+## Settings
+
+`.mergepatrol/mergepatrol.yml` sets the label, the batch size, the conflict resolver, the `verify` commands, and `fix_ci`. Mergepatrol reads it from the default branch, so a change takes effect once its PR merges.
diff --git a/.mergepatrol/mergepatrol.yml b/.mergepatrol/mergepatrol.yml
new file mode 100644
index 0000000..4054695
--- /dev/null
+++ b/.mergepatrol/mergepatrol.yml
@@ -0,0 +1,12 @@
+# Mergepatrol reads this file from the default branch. The dashboard opens a PR to change it.
+version: 1
+label: mergepatrol
+batch_size: 8
+resolver:
+  provider: anthropic
+  model: claude-opus-5-5
+  effort: medium
+verify: []
+fix_ci:
+  enabled: true
+  attempts: 2