> ## Documentation Index
> Fetch the complete documentation index at: https://getpullrequest.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pull requests

> How GPR opens PRs and what is authoritative when GitHub is connected.

After implement and verify, GPR opens or updates a pull request and parks the task in **In review**.

## Source of truth

| Concern                                 | Source                      |
| --------------------------------------- | --------------------------- |
| Branch contents / conflicts from git    | Local daemon git / worktree |
| PR number, state, merged flag on GitHub | GitHub API (when connected) |

Merge-check always runs against **session git** on the machine. GitHub metadata is an enrichment layer, not a replacement.

## With GitHub connected

1. Pipeline reaches `summary_complete`.
2. GPR opens or updates the PR.
3. Task status → `in_review`, checkpoint → `pr_complete`.
4. On merge → `completed` (`PR_MERGED`).

You can review diffs and merge from the mobile app.

## Without a code host

If there is no host to open a PR on, the run can finish via `NOTIFIED` and mark the task completed without waiting on a PR.

## Reviews

Review comments (GitHub or in-app) can feed back into the task. A rerun or continuation addresses them before opening an updated PR.

See [Review and merge a pull request](/docs/guides/review-and-merge).