Review GitHub pull requests and GitLab merge requests from the file you are reading in Emacs: comment on the current line or region, and jump between the file, the PR diff, the forge topic, the review threads and the browser while keeping file and line.
Built on Forge: the repository, the pull request and the API token all come from Forge, so there is nothing extra to configure.
Commenting, suggestions, navigation, review threads (reply, resolve, delete), draft reviews, single-commit review and the CI status of pull requests work on GitHub and GitLab. GitHub Enterprise Server should work too, but is only covered by unit tests.
- Emacs 29.1 or later
- Forge set up for the repository (
forge-add-repository), with its token in your auth-source, and its pull requests pulled (forge-pull)
From MELPA: M-x package-install RET tether. Or from
the repository: M-x package-vc-install RET https://github.com/gkfabs/tether.
(use-package tether
:ensure t
:hook (after-init . global-tether-mode)
:bind (:map tether-mode-map ("C-c t" . tether-prefix-map)))tether binds no key by default: tether-prefix-map holds the commands,
and every one also works from M-x.
global-tether-mode turns tether-mode on in the files of a repository
whose current branch has a pull request in forge's database. Opening a file
never contacts GitHub or GitLab: the first tether command does.
The tether menu (C-c t @ with the binding above, or @ in
magit-dispatch and forge-dispatch) has every command:
| Key | Command | |
|---|---|---|
c |
tether-comment-line |
comment on the current line or region |
S |
tether-comment-suggest |
suggest a change of the line or region |
F |
tether-comment-file |
comment on the whole file |
f |
tether-visit-file |
the file at the line (the PR head's version when the PR is not checked out) |
d |
tether-visit-diff |
the PR diff, at the hunk of the line |
t |
tether-visit-topic |
forge's buffer of the pull request |
b |
tether-browse |
the PR diff in the browser, at the line |
P |
tether-browse-ci |
the CI of the PR at point (in a list of PRs) or of the buffer, in the browser |
m |
tether-visit-status |
magit-status |
v |
tether-pullreq-open |
pick any pull request and open its diff |
C |
tether-commit-review |
review the commit at point alone |
u |
tether-pullreq-open-url |
review the pull request of a URL copied from the browser; a comment link also shows its thread |
l |
tether-thread-list |
the review threads, by file |
. |
tether-thread-show |
the thread of the current line: every comment, and a reply area below (tether-thread-reply is the same) |
H |
tether-thread-toggle-resolved |
show or hide resolved threads in files |
R |
tether-thread-resolve |
resolve the thread at point, or reopen it |
e |
tether-comment-edit |
edit one of your comments in the thread of the line (C-c C-e in a thread window) |
k |
tether-comment-delete |
delete one of your comments, after confirmation |
w |
tether-review-start |
start a draft review: comments are drafts until submitted |
W |
tether-review-submit |
publish the drafts as a comment, an approval or a change request |
X |
tether-review-discard |
delete the draft review |
A |
tether-review-approve |
approve the pull request |
n, p |
tether-thread-next, tether-thread-previous |
go from thread to thread, across files |
s, g, x |
show, refresh, forget what tether knows about the PR |
Comments are written in a Markdown buffer showing the hunk for reference:
C-c C-c sends, C-c C-k cancels, C-c @ mentions someone, C-c C-s
adds or removes a suggestion block, and M-p/M-n bring back text that
was not sent. When posting fails, the buffer stays open and says why.
A line can take a comment when it is in the pull request diff (a changed line, or one of the three lines around it), and has not changed locally since the PR head: tether maps lines through uncommitted and unsaved edits. On GitLab, any line of a file the merge request changes can take one, and a comment may cover lines of several hunks, as in GitLab's web interface; GitHub only takes lines of one hunk. In the PR diff, removed lines can be commented too. With a prefix argument, commands let you pick the pull request.
The mode line shows the pull request (#12 on GitHub, !12 on GitLab),
with ⚠ when the local branch is not the PR head. Once tether resolved the
PR, the fringe marks the lines that can take a comment.
Review threads are fetched in the background once the pull request is
resolved, and again after each comment. They show on their line, with a
fringe mark and the start of the discussion at the end of the line
(resolved ones dimmed; tether-show-resolved, tether-thread-summary), and the mode line counts
the open ones (!540·3). The thread list keeps outdated threads apart,
with the hunk they were written on.
The PR diff (tether-visit-diff, or a magit diff of the same range) shows the
open threads in full under their line, removed lines included, and n/p
go from thread to thread there. So does magit's commit buffer (RET on a
commit in the log), when the commit belongs to a pull request tether
resolved: the threads written on that commit, and those whose line has not
changed since. Comments from there go on that commit, as with
tether-commit-review. tether-diff-thread-comments set to nil shows
only the start of each thread.
Pressing g in magit-status also fetches the CI status of the open pull
requests (GitLab's head pipeline, GitHub's checks), in one request per
repository, and shows it at the end of each line of forge's pull request
list: ✓ passed, ✗ failed, ● running, ⊘ canceled or skipped. The mode line
shows the one of the buffer's pull request (!540·3✓); tether-pullreq-refresh
fetches it too. Nothing else does: a magit-status refreshing by itself,
after a commit for example, shows what was fetched last.
tether-ci-status set to nil turns it off. On a branch without a pull
request, this needs global-tether-mode.
A draft review lives on the forge: GitHub's pending review, GitLab's draft
notes, so one started in the web interface works too. The mode line shows
its drafts (!540✎3). On GitLab, a change request makes you a reviewer if
you are not one (tether asks first), and tether checks it was recorded.
On GitHub, while you have a pending review (started on github.com), comments are added to it: GitHub refuses single comments then.
Version 0.2.0 renamed the commands so that each starts with what it acts
on: tether-comment-…, tether-thread-…, tether-review-…,
tether-visit-…, tether-pullreq-…. The keys did not change, and the
former names (tether-nitpick, tether-diff, …) still work, with a
warning, until a later release removes them.
code-review, emacs-pr-review and github-review review in a buffer of their own, built from the diff. tether comments from the file you are reading, and leaves the repository, the pull request and the token to Forge.
CI runs against two dependency sets:
| Set | magit | forge | ghub |
|---|---|---|---|
min |
latest release (4.7.1 on 2026-10-08) | 0.6.0 | 5.3.0 |
latest |
MELPA snapshot | MELPA snapshot | MELPA snapshot |
Package-Requires can only express minimum versions. If you pin packages
(straight.el or elpaca lockfiles, Nix), pin within this range. If tether
warns that magit/forge/ghub changed, run M-x tether-check-dependencies
and report the output.
Needs Eask.
make deps # latest dependency set
make all # compile, lint, surface check, tests
make deps all TETHER_DEPS=minmake surface fails when the code uses a magit/forge/ghub symbol that is
internal or not in the allowlist in tether-deps.el.
tether is written with the help of an AI assistant (Claude), and each file
says so in its header (Assisted-by:). The author designs it, reviews the
changes and uses it on real pull requests; the tests and CI above check
every change.
GPL-3.0-or-later.