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
Automatically advance to next file after marking file as viewed #5537
When I mark a file as viewed while reviewing, I'd like it to automatically switch to the next file in the list. This will make it so I can just keep my mouse in the top right panel without having to jump back and forth between the sidebar while reviewing. Is this something that currently exists, or are there any alternatives you'd recommend I try? If not, could this be added as an option to the extension?
Thank you for your suggestion Alex Ross (@alexr00). I gave it a shot but I don't think it will work out for me for a few reasons:
If I already started to review the pull request, I have to manually close out of the files I have already reviewed
Often times I've noticed that it will not go in order when I close a file, it will just jump me to some other file a lot further down (I think this is just due to how VSCode handles closing the active file)
It's just a mess to have that many files open at the same time
I think my proposed setting to just automatically open the next unreviewed file will still be the most ideal option.
I came to request this exact thing. I'm trying to find an efficient way to review large prs (like 500+ files changed) and this extension seems like one of the better ways but it's a pain to actually move through all the files. It would be perfect if it automatically advanced to the next file once one is marked as viewed, similar to how it collapses in the Github interface (which sucks for large PRs too)
Alternatively if #5092 was addressed the "Go to next Diff" would actually work alongside the Mark as viewed and be halfway to this solution.
The command to "Open All Diffs" is also a bad solution for any PRs larger than a handful of files because it opens each diff individually in a new tab. It might be usable if it opened all the diffs in a single view like in the web interface but opening hundreds of tabs makes VSCode unusable.
This is so needed!
Existing command "Go to Previous Diff in Pull Request" is broken (it requires you to pull the request in your git AND it jumps randomly on the file tree!).
Why I need to use a mouse to review PR in an IDE that is loaded with shortcuts?!
Activity
alexr00 commentedon Dec 12, 2023
I like to close all files, then use the "GitHub Pull Request: Open All Diffs" command and then "Mark as viewed" to accomplish something similar.
asportnoy commentedon Dec 12, 2023
Thank you for your suggestion Alex Ross (@alexr00). I gave it a shot but I don't think it will work out for me for a few reasons:
I think my proposed setting to just automatically open the next unreviewed file will still be the most ideal option.
jjspace commentedon Mar 4, 2025
I came to request this exact thing. I'm trying to find an efficient way to review large prs (like 500+ files changed) and this extension seems like one of the better ways but it's a pain to actually move through all the files. It would be perfect if it automatically advanced to the next file once one is marked as viewed, similar to how it collapses in the Github interface (which sucks for large PRs too)
Alternatively if #5092 was addressed the "Go to next Diff" would actually work alongside the Mark as viewed and be halfway to this solution.
The command to "Open All Diffs" is also a bad solution for any PRs larger than a handful of files because it opens each diff individually in a new tab. It might be usable if it opened all the diffs in a single view like in the web interface but opening hundreds of tabs makes VSCode unusable.
andrew-lis commentedon Jun 13, 2025
This is so needed!
Existing command "Go to Previous Diff in Pull Request" is broken (it requires you to pull the request in your git AND it jumps randomly on the file tree!).
Why I need to use a mouse to review PR in an IDE that is loaded with shortcuts?!
alexr00 commentedon Dec 10, 2025
/duplicate #4424