---
title: "Create, check and merge PRs from microManager"
description: "microManager creates pull requests through your agent and the GitHub CLI, shows CI checks and review state, and merges with squash, merge or rebase."
url: "https://micromanager.win/features/pull-requests"
updated: "2026-11-08"
---

# Pull requests without leaving the app

When a workspace is ready, Create PR asks the agent to commit, push and open a pull request with the GitHub CLI against the workspace’s target branch. microManager then shows the pull request’s checks, review state and mergeability, and merges it for you.

Updated 8 November 2026

![A Grok chat that committed its work as Add balanceText to each account on GET /accounts, a terminal showing that commit on accounts-balance-text with no upstream, and the Checks panel saying the branch was never pushed and that the GitHub CLI is not signed in, with gh auth login to copy.](https://micromanager.win/screenshots/pull-request-checks.png)

Before there is a pull request, the Checks panel shows what the branch still needs: here a first push and a signed-in GitHub CLI.

## How does Create PR work?

**Create PR** sends the agent in the current chat a prompt asking it to commit the work, push the branch and run `gh pr create` against the workspace’s target branch. Because the agent wrote the code, it can write a meaningful title and description. The prompt is yours to change in Settings → Prompts.

## How do I follow CI and reviews?

Once a pull request exists for the workspace’s branch, the header’s pull request button shows its number and state, and the **Checks** panel lists every check with its status and a link, plus whether the pull request can be merged and its review decision. microManager refreshes this every minute for the workspace you have open and every five minutes for the others, and the sidebar badge shows its number, colored by its checks while it is open, or Draft, Merged or Closed.

When checks fail, ask the agent to fix them; the fix-errors prompt in Settings → Prompts is there for that.

## How do I merge?

**Merge…**, in the pull request button’s menu, runs `gh pr merge` once you confirm the method: **Squash and merge**, **Create a merge commit** or **Rebase and merge**, starting from the one set in Settings → General → Merge method. A draft has to be marked ready for review first. Turn on **Archive after merging** in Settings → General to archive the workspace as soon as a merge from microManager goes through, which removes the worktree and keeps the branch and any uncommitted work.

## Which branch does the pull request target?

The workspace’s target branch, shown as **→ target** in the header. It starts as the repository’s default branch; pick another before creating the pull request if the work belongs elsewhere.

## Where to go next

- [Diff review](https://micromanager.win/features/diff-review)
- [Workspaces and archiving](https://micromanager.win/docs/workspaces)

## Frequently asked questions

### Do I need the GitHub CLI?

Yes, for pull request features. Install gh and run gh auth login once; microManager uses whichever account gh is signed in to. Everything else in microManager works without it.

### Can I change how the agent writes pull requests?

Yes. The create-PR prompt is editable in Settings → Prompts, alongside the prompts for code review, fixing failing checks, resolving conflicts and renaming branches, and a repository can have its own in Settings → Repositories.

### Does it work with GitLab or Bitbucket?

No. Pull request features use the GitHub CLI, so they work with GitHub repositories. Git itself works with any remote.