The review

A review is Tern’s read of a pull request, posted on the PR as a comment. Install the webhook once on a repo, and Tern posts that read where the change is reviewed.

The comment lists the open decisions and the issues worth a look, each with why and links to the lines, plus a link to the tour. Decisions you already accepted stay off it, and it never quotes the agent session.

kvantern commented 3 days ago · edited

Author···

Tern Risk Report

range 92fc308b→9264170f

1 decision (1 open) · Open the tour

Decisions

1.Apply the filter in realtime ingest, but not batch processing.

customers

Why review: One of the two paths still returns other customers' rows.
Rejected alternative: Use the same filter on both paths.
Where: internal/query/filter.go:40-58

Installing

You need to be an admin of the GitHub repo.

tern install github-webhook owner/name

The repo has to be linked already (tern repo add). Once the webhook is installed, a review fires on every PR whose author is running Tern. Tern needs that author’s sessions to tie the review to the code.

--replace installs a fresh webhook when one is already there. --org matters only when that repo is linked in more than one org.

Posting one yourself

On the branch you have checked out:

tern risk run --post

Push first, so the comment matches the PR. This needs a local agent running so the tour link exists.

How the comment is posted

The service posts the comment. Append is the default: a new comment on each push. Single keeps one comment and updates it. tern risk run --post always uses single. Set service.work_pr_tour.comment_style to single or append in ~/.tern/agent.yaml.

Timing

Creating a pull request starts a review immediately. A push to an existing pull request waits for the branch to settle, so the comment can lag that push by up to 15 minutes.