Your pull request can wake the terminal
GitHub CLI can listen for pull request events in preview. A green check arriving for yesterday’s code shows why listening is only half the job.

The terminal that knows when to wake up
Imagine putting a cake in the oven and walking over to the kitchen every thirty seconds to see whether the timer has rung. That is roughly how some scripts wait for a pull request. They wake up, ask the server whether anything changed, go back to sleep and do it all again. A quiet afternoon can generate a remarkable number of requests whose only useful answer is “nothing yet.”
On 18 November, GitHub announced support for Event Streams in version 2.105.0 of its command line tool. With preview access on GitHub.com, a developer can run gh event listen for a pull request and select the events they care about. By default the command prints the first matching event as a line of JSON and exits. The announcement directs developers to a waitlist for the service. Installing the new CLI is only one part of trying the feature.
Source: GitHub announcement
What a timer costs
Take a hypothetical team with twelve open requests, each checked once every thirty seconds. In ten quiet minutes that is about twenty checks per request, or 240 checks across the team. Now a reviewer responds just after one of those checks. The script can spend nearly thirty more seconds asleep before it notices. Checking more often reduces that delay at the price of more empty conversations. Waiting for an event changes the arrangement. The listener asks to be told when something interesting happens.
What counts as interesting depends on the job. A contributor waiting for a human review might care about a submitted review. A display showing whether tests have finished might care about a completed check suite. A script that reacts to everything and prints an enthusiastic message for every change soon recreates the noise it was supposed to remove. Pick the decision you want to make before choosing the event you want to receive.
The green light belonged to another train
Here is a paper exercise. On a card write that revision A passed its tests. On another write that a contributor has just pushed revision B. Hand both cards to a friend, once in chronological order and once in reverse. If their rule is “show green when a passing result arrives,” one ordering can leave the display green for a revision nobody has tested. Every individual statement on the cards is true. The mistake is attaching a true statement to the wrong version.
A better display keeps the revision alongside the result and checks which revision the pull request currently points to. When the connection returns after a laptop sleeps, read the current state again before refreshing the display. That one read has a purpose. It settles what is true now, including changes that might have happened while the listener was away.
Give silence an ending
A small automation is easier to live with when its owner can tell the difference between waiting normally and waiting forever. Give the listener a reasonable time limit. Decide whether reaching that limit should prompt another state check, a polite message or simply an exit. For a first experiment, write three possible terminal messages on paper first. One describes a matching review, one describes a changed revision and one describes an uneventful timeout. You have just designed most of the behavior a teammate will actually notice.