You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Finding how to submit pending review comments is VERY hard #8751
Repository Clone Configuration (single repository/fork of an upstream repository): Single repo
GitHub Product (GitHub.com/GitHub Enterprise version x.x.x): github.com
Steps to Reproduce:
Check out a PR branch
Use the "GitHub Pull Request" sidebar view to navigate files and add pending comments in the editor
Struggle to find the "submit review" button
Google how to do it, which suggests it should be in the command palette ... it is not
Give up and go submit the pending review with a web browser
Do this again 4 or 5 times
Eventually discover that the embedded webview version of the PR can submit the pending comments
Why is there no more accessible button to submit the pending review? Loading the full web view for the PR is both non-discoverable, and it certainly feels like a very heavy weight and obtuse way to show a text box and 3 buttons.
I only even found that because of random right-clicking on things to see what the extension could do, and randomly came across Open Pull Request Description To The Side and clicked it purely out of curiosity, having no expectation that it would provide the only means I've found so far of surfacing the "Submit Review" button.
Alex Ross (@alexr00) The Review Pull Request ... pane doesn't show for me at all. In the sidebar panel for the github pull requests extension, the only available panes are Changes in Pull Request and Comments. I checked in the ... menus there in case I had accidentally hidden that pane before, but it's not listed.
I was wondering if this is a preference I have changed, but I don't think so. I didn't see any preference for the extension that looks like it would do this, and these are the only prefs I have overridden for the extension:
This is helpful, thanks! We don't show the "Review Pull Request #` view if you are in a multi-repo workspace and have multiple PRs checked out, as it doesn't have a lot of screen real-estate so show info for multiple PRs in.
I'll need to think about how else we could prompt users to find the "submit" button.
there's only one root in it currently, and thus only one PR is / can be checked out
Ok, then I think we're back to it being multi-repo, not multi-root. Is it at all possible that you have more than one GitHub repository open? Like, maybe you opened even just a single file from another repo? Do you see more than one repo in the SCM view?
After mucking about searching through the extension source, it appears the issue is the githubPullRequests.focusedMode setting. I had changed this to false, because having the vscode window flop around madly whenever I ran git from the command line was infuriating, and I was trying to figure out which settings caused that. The changelog entries for this setting suggest it was part of my problem, though I'm not sure if it still is.
Either way, having that setting make the sidebar panel non-functional seems weird, as the setting description seems like it's mostly focused on opening "editor" area views?
I really dislike having my command line git activities cause random editor views to open, so I don't want to have to bring that back.
Edit: yeah, resetting that setting is infuriating. Now even things like git commit from the command line not only cause the vscode window layout to change, but it steals focus from the terminal, so it has me unintentionally start typing into a diff view instead of the terminal. Yuck. That setting behaves as if I either never want to review PRs in VScode, or as if I never do anything else.
Now even things like git commit from the command line not only cause the vscode window layout to change, but it steals focus from the terminal, so it has me unintentionally start typing into a diff view instead of the terminal.
This should not be happening. Can you give some exact steps (what branch were you on, did the branch have a PR, etc. )?
This should not be happening. Can you give some exact steps (what branch were you on, did the branch have a PR, etc. )?
I had a branch checked out associated with a PR. I had been doing work and had various uncommitted changes. I had previously had the github pull request panel open, but now had a different panel selected in the sidebar. I used git commit to commit my work from the terminal. As soon as the git command completed, the sidebar was switched to the github pull request panel, the multidiff editor for the PR was opened, and took focus, so that the command I was starting to type into the terminal instead went into one of the files from the PR. That layout change & focus steal happened almost instantly, i.e. within less than a second of the git command completing.
I just had it change layout and steal focus again, this time without even editing any files or running any git or other commands in the terminal. It just randomly changed layout and stole input focus while I was typing into a different extension in the secondary sidebar.
Extension output log for the relevant time period (private data censored to NNNN / BRANCH / etc.)
2026-07-02 11:09:40.323 [info] [Review+0] Polling for state change...
2026-07-02 11:09:40.639 [info] [Review+0] Polling detected potential new PR activity while a PR is active. Refreshing state.
2026-07-02 11:09:40.639 [info] [Review+0] Validate state in progress
2026-07-02 11:09:40.639 [info] [Review+0] Validating state...
2026-07-02 11:09:40.676 [info] [FolderRepositoryManager+0] Found GitHub remote for folder /workspaces/REPO
2026-07-02 11:09:40.676 [info] [FolderRepositoryManager+0] Using in-memory cached mentionable users.
2026-07-02 11:09:40.676 [info] [FolderRepositoryManager+0] Using in-memory cached assignable users.
2026-07-02 11:09:41.015 [info] [Review+0] Skipping GitHub check for branch fix/BRANCH: no new PRs since last check
2026-07-02 11:09:41.015 [info] [Review+0] Found matching pull request metadata for current branch fix/BRANCH. Repo: ORG/REPO PR: NNNN
2026-07-02 11:09:41.015 [info] [Review+0] current branch fix/BRANCH is associated with pull request #NNNN
2026-07-02 11:09:41.015 [info] [Review+0] Resolving pull request
2026-07-02 11:09:43.041 [info] [GitHubRepository+0] Fetch branch main - enter
2026-07-02 11:09:43.334 [info] [GitHubRepository+0] Fetch branch main - done: true
2026-07-02 11:09:43.334 [info] [Review+0] Resolved PR #NNNN, state is OPEN
2026-07-02 11:09:43.334 [info] [Review+0] Fetching pull request data
2026-07-02 11:09:43.334 [info] [PullRequestTree] Adding PR #NNNN to tree
2026-07-02 11:09:43.334 [info] [PullRequestTree] PR #NNNN already exists in tree
2026-07-02 11:09:43.334 [info] [Review+0] Register comments provider
2026-07-02 11:09:43.348 [info] [Review+0] Register in memory content provider
2026-07-02 11:09:43.348 [info] [Review+0] Display pull request status bar indicator.
2026-07-02 11:09:43.348 [info] [Review+0] Using focus mode = true.
2026-07-02 11:09:43.348 [info] [Review+0] State validation silent = false.
2026-07-02 11:09:43.348 [info] [Review+0] PR show should show = false.
2026-07-02 11:09:43.348 [info] [FolderRepositoryManager+0] Using in-memory cached assignable users.
2026-07-02 11:09:43.410 [info] [Review+0] Polling detected change. Next poll in 300s.
2026-07-02 11:09:43.580 [error] [Jv] Already updating pull request view
2026-07-02 11:09:44.076 [info] [PullRequestTree] Local files have changed, refreshing Files node
2026-07-02 11:09:44.110 [info] [PullRequestTree] Getting children for Files node
2026-07-02 11:09:44.110 [info] [PullRequestTree] Got all children for Files node
2026-07-02 11:09:44.410 [info] [PullRequestTree] File viewed state has changed, refreshing Files node
2026-07-02 11:09:44.431 [info] [PullRequestTree] Getting children for Files node
2026-07-02 11:09:44.431 [info] [PullRequestTree] Got all children for Files node
2026-07-02 11:09:44.644 [info] [PullRequestTree] Review threads have changed, refreshing Files node
2026-07-02 11:09:44.644 [info] [PullRequestTree] Review threads have changed, refreshing Commits node
2026-07-02 11:09:44.645 [info] [PullRequestTree] Comments have changed, refreshing Files node
2026-07-02 11:09:44.645 [info] [PullRequestTree] Comments have changed, refreshing Commits node
2026-07-02 11:09:44.667 [info] [PullRequestTree] Getting children for Files node
2026-07-02 11:09:44.667 [info] [PullRequestTree] Got all children for Files node
2026-07-02 11:09:45.006 [info] [PullRequestTree] Getting children for Files node
2026-07-02 11:09:45.006 [info] [PullRequestTree] Got all children for Files node
What changed (I think) on the PR was a new code review was submitted.
Thank you for the info! I regressed this 3 months ago. Fix is now on main, and there's a new pre-release build going now (should be available within 30 min if you want it). Next stable release will be available by Wednesday.
It isn't supposed to be. We should only be doing layout changes when you check out a PR from the one of the PR extension UI entry points. Can you confirm which pre-release version you have, and can you share the output of GitHub Pull Request next time you get an unexpected layout change?
Matthew Gabeler-Lee (@fastcat) thank you for your help tracking this down! I have made another fix (available in the latest pre-release, requires the latest VS Code insiders again). Please let me know if it resolves the issue.
Activity
alexr00 commentedon Jun 3, 2026
You can submit it from the sidebar when you have it checked out (circled).
We've gotten this feedback before, so we have a "Go to Review" button in the comment widget (squared).
Where else did you click around to try to find it? Maybe I can add something in the places you looked.
fastcat commentedon Jun 5, 2026
Alex Ross (@alexr00) The
Review Pull Request ...pane doesn't show for me at all. In the sidebar panel for the github pull requests extension, the only available panes areChanges in Pull RequestandComments. I checked in the...menus there in case I had accidentally hidden that pane before, but it's not listed.I was wondering if this is a preference I have changed, but I don't think so. I didn't see any preference for the extension that looks like it would do this, and these are the only prefs I have overridden for the extension:
And for the avoidance of any potential confusion, here's what the panel specifically looks like for me:

alexr00 commentedon Jun 8, 2026
This is helpful, thanks! We don't show the "Review Pull Request #` view if you are in a multi-repo workspace and have multiple PRs checked out, as it doesn't have a lot of screen real-estate so show info for multiple PRs in.
I'll need to think about how else we could prompt users to find the "submit" button.
fastcat commentedon Jun 8, 2026
I'm this case, while I have a workspace open, there's only one root in it currently, and thus only one PR is / can be checked out
The workspace mainly exists so I can color code different windows without polluting the repo with my personal cosmetic choices
alexr00 commentedon Jun 8, 2026
What do you see if you right click on the "CHANGES IN PULL REQUEST #..." title?
fastcat commentedon Jun 8, 2026
I get
Changes In Pull RequestandCommentsonly, notReview Pull Requestalexr00 commentedon Jun 12, 2026
Do you have a command "GitHub Pull Request: Focus on Review Pull Request View" in the command palette?
fastcat commentedon Jun 12, 2026
I do not, see item 4 in the original description
alexr00 commentedon Jun 12, 2026
Ok, then I think we're back to it being multi-repo, not multi-root. Is it at all possible that you have more than one GitHub repository open? Like, maybe you opened even just a single file from another repo? Do you see more than one repo in the SCM view?
fastcat commentedon Jun 12, 2026
No, there is only one root and only one repo open:
alexr00 commentedon Jun 15, 2026
Could you share the output from GitHub Pull Request?
fastcat commentedon Jun 15, 2026
(private info censored as XYZZY, QUUX, and NNNN)
fastcat commentedon Jul 1, 2026
After mucking about searching through the extension source, it appears the issue is the
githubPullRequests.focusedModesetting. I had changed this tofalse, because having the vscode window flop around madly whenever I rangitfrom the command line was infuriating, and I was trying to figure out which settings caused that. The changelog entries for this setting suggest it was part of my problem, though I'm not sure if it still is.Either way, having that setting make the sidebar panel non-functional seems weird, as the setting description seems like it's mostly focused on opening "editor" area views?
I really dislike having my command line git activities cause random editor views to open, so I don't want to have to bring that back.
Edit: yeah, resetting that setting is infuriating. Now even things like
git commitfrom the command line not only cause the vscode window layout to change, but it steals focus from the terminal, so it has me unintentionally start typing into a diff view instead of the terminal. Yuck. That setting behaves as if I either never want to review PRs in VScode, or as if I never do anything else.alexr00 commentedon Jul 2, 2026
This should not be happening. Can you give some exact steps (what branch were you on, did the branch have a PR, etc. )?
fastcat commentedon Jul 2, 2026
I had a branch checked out associated with a PR. I had been doing work and had various uncommitted changes. I had previously had the github pull request panel open, but now had a different panel selected in the sidebar. I used
git committo commit my work from the terminal. As soon as thegitcommand completed, the sidebar was switched to the github pull request panel, the multidiff editor for the PR was opened, and took focus, so that the command I was starting to type into the terminal instead went into one of the files from the PR. That layout change & focus steal happened almost instantly, i.e. within less than a second of thegitcommand completing.fastcat commentedon Jul 2, 2026
I just had it change layout and steal focus again, this time without even editing any files or running any git or other commands in the terminal. It just randomly changed layout and stole input focus while I was typing into a different extension in the secondary sidebar.
Extension output log for the relevant time period (private data censored to NNNN / BRANCH / etc.)
What changed (I think) on the PR was a new code review was submitted.
alexr00 commentedon Jul 3, 2026
Thank you for the info! I regressed this 3 months ago. Fix is now on
main, and there's a new pre-release build going now (should be available within 30 min if you want it). Next stable release will be available by Wednesday.fastcat commentedon Jul 6, 2026
Thanks! I've updated to the pre-release version and will confirm here (and on #8826) once I have results
fastcat commentedon Jul 7, 2026
It's better, e.g.
git commitdoesn't trigger layout changes, but things like switching branches still do.I don't understand why having the usable sidebar layout is tied to having it change layout and steal focus.
alexr00 commentedon Jul 9, 2026
It isn't supposed to be. We should only be doing layout changes when you check out a PR from the one of the PR extension UI entry points. Can you confirm which pre-release version you have, and can you share the output of GitHub Pull Request next time you get an unexpected layout change?
fastcat commentedon Jul 13, 2026
logs:
alexr00 commentedon Jul 16, 2026
Matthew Gabeler-Lee (@fastcat) thank you for your help tracking this down! I have made another fix (available in the latest pre-release, requires the latest VS Code insiders again). Please let me know if it resolves the issue.