Merge Desk · Judge's guide
Try it without signing in
Merge Desk resolves a pull request's merge conflict with Gemini, then refuses to land the result until it parses, keeps what each side chose to keep, and passes the repository's real tests. The demo replays real runs on three conflicting pull requests. Open each one below; the analysis and every check play back at their original pace.
Open the demoDemo links open in a new tab, so this guide stays open.
1.A held merge
[Demo] Add a minimum charge and late fees (#2)
- Press Run checks on the recommended option, Combine both.
- Gemini's merge parses and keeps what both sides changed, but the repository's real tests fail: code outside the conflicted file still calls the old signature. The result is HELD, with the failing check and the tests' own output. Nothing is pushed, and the hold is written to the pull request's decision record.
- Steer and retry with the recorded line, "Keep the old call working too.". This time Gemini's merge leaves out lines from both sides, and the choice-honored check catches it: ours and theirs MISSING, HELD again.
- The other options on the slider are held too.
2.A verified merge
[Demo] Rename fetchUser to getUser (#1)
- Run Combine both. It parses, both branches' changes are present, and the tests pass: VERIFIED.
- Press Land. This replays a real Land: the merge commit went onto the pull request's own branch, never its base, and the decision record gained an entry. The branch was reset afterwards so the demo can start over.
3.A chosen drop
[Demo] Parse price strings in toCents (#6)
- Move the slider to Keep ours, drop theirs. Merge Desk names whose work is dropped and asks you to hold the button (or press Ctrl+Enter) to confirm.
- The run is VERIFIED with theirs "dropped as chosen". Land it, and the decision record lists the dropped commits so the work can be recovered.
- Gemini recommended combining here, and that verifies too: each option is checked against what it says it keeps.
4.Start over
Press Reset in the demo banner. Every pull request starts again.
What is real here
- Every step was recorded on October 7, 2026 from real runs on these pull requests: Gemini (
gemini-3.5-flash-lite) proposed each resolution, and a Vercel Sandbox merged the branches with git, applied the proposal and ran the tests withnode --test. That is 15 recorded runs (6 of them steered retries), 3 VERIFIED and 12 HELD, each taking 10.3 to 12.2 seconds from start to verdict. - Every verified run was landed for real: 3 Lands on the demo pull requests' own branches, each recorded on the pull request and then reset so the conflict is back. Holds and discards were written to the same decision records.
- The demo itself sends no requests and writes nothing. Live mode runs the same pipeline on real pull requests: anyone can sign in with GitHub and use it on a repository where they installed the Merge Desk app and can push.
- VERIFIED means exactly those checks passed. It is evidence, not a proof that a merge is correct.
Check it yourself
- /api/health: whether each integration is configured on this server
- /api/stats: every number above and the command that measured it
- Source on GitHub : pull requests labelled
demoare seeded conflicts that targetdemo/base, nevermain