MergepondDownload
Mergepond
Download for Mac

Free for local repos. macOS 13 or later.

Pull requests

Mergepond checks out a pull request by number into its own worktree, so you can review or run it without disturbing the branch you are on. It works with any remote that serves pull request heads under refs/pull, as GitHub does. There is no pull request list, review or merge inside the app.

Where to find it

  • File › New Worktree from Pull Request…, or ⌘⇧N.
  • Command palette › Worktrees › Create worktree from a pull request.
  • New worktree sheet, with Pull request chosen as the source.
The Worktrees tab, where a pull request checked out this way appears as a card on the branch pr-412.

Checking one out

The New worktree sheet opens with Pull request selected. Type the number into Pull request number (placeholder "412"). The hint reads "Fetched from origin into the branch pr-n". The folder follows the worktree folder pattern; the setup recipe runs if it is ticked. See Worktrees and worktree setup.

Create worktree then:

  1. Fetches pull/412/head from the default remote into a local branch pr-412.
  2. Creates the worktree on that branch.
  3. Runs the setup recipe, if any.

The number is required: "Type the pull request number, like 412." if the field is empty.

The remote is origin, or the only remote if there is no origin. With several remotes and no origin, Mergepond can't choose and says so. If the remote doesn't serve refs/pull/*, the fetch fails with Git's message. If a branch pr-412 already exists, Mergepond checks it out as it is rather than fetching again.

What you get

A branch pr-412 tracking nothing, checked out in its own folder. It behaves like any other worktree: it shows on the board with its changes and commits, you can open it in a window or in Terminal, and the sidebar lists it under the repository.

The branch pr-412 has no upstream, so Pull won't bring in commits pushed to the pull request later, and creating the worktree again reuses the existing branch without fetching. To update it, run git pull origin pull/412/head in the worktree's folder (Open in Terminal), or remove the worktree, delete the branch and create the worktree again.

When the pull request is merged

Once the pull request's commits are in the default branch, the worktree's branch counts as merged and the card moves to Merged or gone. Clean up removes the folder; see Cleaning up merged worktrees. The pr-412 branch stays until you delete it from Sidebar › Branches.

Free and Pro

Checking out a pull request into a worktree works on Free. If the repository is on an SSH host, opening it needs Pro; see Remote repos over SSH.