Core Concepts
GitHub & Pull Requests
er integrates with GitHub through the gh CLI — no API tokens to manage. Open a pull
request, see its CI and reviewer status, sync comments both ways, and push your work, all without opening a browser.
Prerequisites
Install the GitHub CLI and authenticate once:
gh auth login
er shells out to gh and reuses that authentication. There is no separate token to
configure and nothing to register inside er: a missing or unauthenticated gh shows up
as an error on the action you ran, or as an empty PR panel.
Opening a pull request
From the terminal, open a PR by number or by URL:
# by number, in the current repo
er --pr 42
# by full URL, from inside a clone of that repo
er https://github.com/owner/repo/pull/42
# from any directory, no local clone
er --remote https://github.com/owner/repo/pull/42
The desktop app offers a “PR Diff” toggle in the branch context bar and a paste-a-URL modal (Cmd+Shift+O). PR review works against remote refs, so you can review a pull request without checking out its branch into your working tree.
Automatic base detection & the PR hint
When you are on a branch that has an open PR, er notices it. If the PR targets a base branch different
from the one er auto-detected, it shows a hint rather than switching silently — you
stay in control of what you are comparing against. The PR base check runs on a background thread so it never slows
startup.
The PR context panel
In PR mode the right-hand panel summarizes the pull request without a browser round-trip:
- CI checks — build, tests, and other checks with pass/fail/running status.
- Reviewers — who approved, who requested changes, who is still pending.
- Description — the PR body.
- Title & base — e.g.
feat/auth-refactor → main.
Two-way comment sync
GitHub comments (the cyan c notes) sync in both directions. In the terminal:
| Key | Action |
|---|---|
| G | Pull review comments from the PR into your diff view |
| g → Push comments to GitHub | Push your local comments up to the PR — r posts them as one review, i as individual comments |
Pulled comments appear inline, anchored to their lines, alongside your own. Each comment tracks its
source, GitHub id, author, and synced flag. Because
deduplication keys on the GitHub id, pulling repeatedly is safe — you will not get duplicates. Pushing marks your
comments as synced. Replies are single-level threads, matching GitHub's PR review model (see
Comments & Questions).
Publishing your review to a PR
Publishing happens inside er itself. In the TUI, open the Git hub (g)
and choose Push comments to GitHub — r bundles the pending comments into one review,
i posts each on its own; in the Desktop app, open the Comments card and use
Push to GitHub — As review (one submission carrying the pending comments) or
Individually. What GitHub receives is your GitHub comments: AI findings, questions, and notes are private
to your machine until you promote one to a comment in the desktop app. The desktop refreshes the diff before
submitting a review and skips comments whose lines are no longer in it; that submission is the bridge from a
local er session to a review your team sees on GitHub. See
AI Hub Actions.
Staging, committing, and pushing terminal
You can move work along without leaving er:
| Key | Action |
|---|---|
| s | Stage / unstage the current file |
| Ctrl+P | Git push (from staged mode) |
After you commit, er switches to a view of exactly what was committed so you can confirm it. Staging
is file-level. For richer git operations, drop to your shell — er is a review tool, not a full git client.
The desktop app surfaces the same GitHub data through cards (branch status, checks, comments) and can submit reviews from its UI. See Desktop Features.