GitHub CLI Adds Event Streams for Real-Time Pull Request Updates
GitHub CLI v2.105.0 introduces support for GitHub Event Streams, allowing users and automation to listen for pull request events without polling. This functionality is currently in preview and requires joining a waitlist for access.
What changed?
GitHub CLI (gh) v2.105.0 now supports GitHub Event Streams. New commands, including 'gh event listen', allow users and agents to wait for changes to a pull request in real time, such as review submissions, pull request state changes, updates to the head, merge conflicts, or completed check suites. The command prints each event as a JSON line and can be integrated directly into scripts. Additional commands help manage event stream subscriptions. This functionality is available in preview and requires access to GitHub.com's Event Streams feature, which is also in preview and accessible via a waitlist.

Why does it matter to an everyday developer?
Developers and automation no longer need to implement polling loops to detect pull request changes. Instead, they can use a single CLI command to efficiently wait for these events, reducing complexity, excess API calls, and latency in response to repository activity. This makes continuous integration and automation workflows simpler, more efficient, and more responsive.
What can the developer do now?
Developers can upgrade to GitHub CLI v2.105.0 or later, sign up for the GitHub Event Streams waitlist, and start using the new 'gh event' commands once access is granted. To listen for pull request events, run 'gh event listen' with the Pull Request URL and specify events of interest. Options allow waiting for multiple events, following streams, or extracting specific fields for use in automation scripts. Documentation and help are available within the CLI and supporting pages.
