Global technology, grounded in Africa.Reported from London · Connected to the world

The four desks

Stories & formats

More

Find a published story by title, subject or author.

ai tools

GitHub CLI can wait for a review. Read the pull request when it wakes

The new gh event preview lets an agent wait for a pull request event. Check account access, set a timeout and fetch the current review or checks before deciding what to do.

Watch this report

Read the report and video transcript

Media credits, sources and reuse details ↓

An agent has opened a pull request and needs a person to review it. GitHub CLI now offers a command that can wait for that change. Version 2.105.0, released on 18 November, adds `gh event listen` for pull request events. The useful handoff is a bounded wait followed by a fresh read of the review or checks. That gives the next action a current record to work from. GitHub’s release announcement.

Check the account and host first

The commands and Event Streams are in preview. GitHub grants access through a waitlist, per account. Having a recent CLI version alone will leave some accounts without access. The user or installation also needs permission to read the pull request. The documented service covers github.com. GitHub Enterprise Server and GHE.com are outside the CLI’s supported host scope. For a team working between the UK and African offices, verify the account and host used by the actual agent or runner before changing the workflow. Access requirements · CLI host limits.

Name the event and give the wait an end

GitHub’s documented review example uses `gh event listen --resource https://github.com/OWNER/REPO/pull/123 --event com.github.pullrequest.review.submitted.v1 --timeout 30m`. Replace the example URL with the pull request you can access. The command creates or reuses a subscription and, by default, returns after one event. Status messages appear on stderr and event JSON appears on stdout. A timeout returns exit status 8, which the calling script needs to handle. [Command and timeout behaviour](https://cli.github.com/manual/ghevent_listen).

A submitted-review event can follow an approval, a request for changes or a comment. Read the referenced review before deciding which action belongs next. The event includes an API location for the changed object. PING suggests writing the expected outcome into the task handoff, so the agent can check it against the current record. Event meanings.

Read the state after the stream connects

The CLI prints a listening message when the stream attaches. GitHub tells users to read the pull request’s current state at that point. Earlier events are not replayed. If the connection breaks, the CLI reconnects, but changes during the gap can be missed. Recheck the current state when recovering from a dropped connection, particularly before an unattended process resumes work. Connection and replay rules.

A check-suite event needs the rest of the checks

The supported check event is `com.github.pullrequest.checksuite.status.changed.v1`. It arrives when a check suite on the head commit completes, whatever its conclusion. A pull request can have several suites, and reruns produce further completion events. Read the aggregate checks after each notice, for example with `gh pr checks`, before treating the requested check set as complete. Check-suite scope.

The listener leaves its subscription in place when it exits. Subscriptions expire after 24 hours, and GitHub documents a limit of 100 active subscriptions per user, app and installation token. Use the subscription list to inspect what is active, and remove subscriptions the workflow has finished using. During this preview, keep the event names, access assumptions and recovery behaviour beside the script so another operator can maintain it. Subscription lifecycle and limits.

Read PING! on checking what happens when an agent retries.

Video transcript

Original PING! Magazine graphics, captions and edit. British English synthetic narration by Kokoro Emma (bf_emma). A new command can wait for a pull request review. Check preview access before you use it. Set a time limit for the wait. A timeout returns status eight. Handle that result in your script. Read the current pull request after the stream connects. Earlier events are not replayed. When a check finishes, read all the checks. Read the state again if the connection drops.

Sources and disclosures
Disclosure
Documentation-based reporting with AI-assisted drafting. PING retrieved GitHub’s release, CLI manual and Event Streams documentation on 19 November 2026. PING did not subscribe to a live repository or test event delivery. The cover and video use original explanatory graphics. Video narration uses the Kokoro Emma synthetic voice.
Declared media rights
Generated illustration
Sources and method
GitHub CLI 2.105.0 was released on 18 November 2026 at 00:18:35 UTC. The launch post displays 18 November in Pacific time and carries 19 November 00:00:13 UTC publication metadata. GitHub Event Streams remains a waitlist preview. Example owner/repository/PR are placeholders. The article distinguishes review notification, current review state and aggregate check completion. Cover: GitHub’s documented review wait needs preview access and a fresh state read after the stream attaches. Example owner, repository and pull-request number are placeholders. Original graphic by PING! Magazine. Command behaviour from GitHub CLI and GitHub Docs. Video: A 25-second PING guide with original diagrams and Kokoro Emma synthetic narration. Original diagrams, script and edit by PING! Magazine. British English synthetic narration by Kokoro Emma (bf_emma). Command behaviour from GitHub CLI and GitHub Docs. Media provenance: Video -- Generated illustration. Cover -- Owned by PING!.

Reader comments

Comments are not open yet. When available, submissions will require free sign-in and editorial approval before appearing. PING does not promise a response.

Privacy information