Repository navigation
Stacked PRs: PR state does not change in stack unless you manually change the webview #9020
Description
Testing #9011
In the following screenshot, the Otacon updates 1 PR is actually ready for review. I expected the view to eventually update with the correct state of the PR, but you need to update the webview in some way to get it to work (ie, navigate to another PR in the stack, then each PR's state will update accordingly)
Edit: Perhaps this is what the refresh button towards the top is for 🙃 . Feel free to close, otherwise this is a feature request to have this webview update without me having to refresh
Activity
bryanchen-d commentedon Oct 12, 2026
Verified the stack refresh/rendering path in an isolated before-and-after regression test of #9021.
Compared the pre-fix base
7b7ccebbe4b05c46f461752389cd25c3b142b4b6with the fixed PR head52fb0dd3376c51f5894c7318d96c4ecb487432fd. In both runs, a sibling PR's model changes from draft to ready while another PR's stack view remains open.The screenshot captures the actual production React stack component, original component CSS and SVGs, connected through production model, repository-event, refresh and webview message-handler code. PRs #999 and #1000 are synthetic fixtures, not live repository PRs.
Verification scope: GitHub APIs and VS Code host services are mocked. This verifies the observed-model-change-to-rendered-badge path without manual overview refresh or navigation. It does not establish that an external GitHub change is automatically detected in an authenticated, idle VS Code session.