pullfrog watch streams a pull request’s activity to your terminal — one structured event per new review, comment, inline review thread, PR state change, or check-suite completion. It exists so a tool or agent babysitting a PR never has to poll the GitHub API in a loop: Pullfrog already receives every relevant GitHub webhook, so it fans those events out to you the instant they fire, with sub-second latency and zero GitHub rate-limit spend.
Usage
Run it from inside your repo:--pretty for a human-readable line instead of JSON.
Options
| Flag | Description |
|---|---|
--pr <number> | pull request number to watch (required) |
--since <cursor> | resume from a cursor emitted by a prior event |
--pretty | human-readable output instead of JSON lines |
-h, --help | show help |
Event kinds
Every line carries akind, the affected pr, an ISO createdAt, an opaque cursor, and a curated data object. The kind is one of:
| Kind | Fires on |
|---|---|
pr | pull request opened / closed / synchronized / edited / labeled / etc. |
review | a review submitted, dismissed, or edited |
review_comment | an inline review comment created, edited, or deleted |
review_thread | an inline review thread resolved or unresolved |
comment | a top-level comment on the PR |
check | a check suite completed (carries status + conclusion) |
data holds just enough to decide whether to react (actor, action, state, a truncated body/title, and the html_url); fetch full detail on demand from the url.
Resuming
The stream is cursor-based. Each event carries acursor; if your process restarts, pass the last one you saw as --since <cursor> to pick up exactly where you left off without replaying what you already handled. A fresh watch with no --since starts from now — it does not replay history.
Authentication
watch authenticates with your GitHub token (from gh auth token) and only streams events for repositories that token can read. Make sure the GitHub App is installed on the repo and you’re signed in with the GitHub CLI: