Pull request integration in Visual Studio has been one of the most requested Git features. Developers have been asking for a way to open a PR, inspect the changes, discuss feedback, and finish the review without switching to the browser. The feedback on that request has played a big role in shaping this experience over time.
You’ve been able to create pull requests in Visual Studio since 2024. Now you can also review, comment on, and approve pull requests from both GitHub and Azure DevOps, all without leaving the IDE.
Find and open pull requests
You can view the list of pull requests for the open repository from the Git Repository window, the Git Changes window, or the Git menu. If your current branch already has an active PR, you can also open it directly from Git Changes.
When you open a pull request, you can see the overview, changes, commits, and reviewers together in one place. If a teammate asks for a quick review, you can open Visual Studio, find the PR, and get straight to what you need.
From there, you can choose how deep you want to go. You can review the pull request without checking out the branch, which lets you inspect the changes while keeping your current branch, uncommitted changes, and working state intact.
If you want a closer look, you can also check out the PR branch and use Visual Studio’s navigation, build, and debugging tools to dig into the code. Reviewing without checking out is great for a quick pass, while checking out the branch is better when you want to investigate more deeply.
When you’re juggling multiple reviews, you can switch between active pull requests without having to check out all of them. That makes it easier to jump in on reviews during the day, then get back to your own work.
Browse the changes
The pull request view is designed to help you move through a pull request quickly. Open any changed file to see the diff inline or side by side, or use the multi-file summary view to see all changes at a glance.
Tip: If you want a wider view of the diff, collapse the left panel and focus on the code.
You can also review commit by commit, which is useful when a pull request covers several logical steps and you want to understand how the change evolved.
Comment and discuss
You can leave comments on specific lines, reply to threads, and resolve conversations when the discussion is done. Files with active comments are marked in the Changes list, so it’s easy to spot where discussions are happening. Everything syncs between Visual Studio and the browser.
When you’re reviewing a pull request in checked-out code, you can apply a code suggestion directly to your working copy with one click. When there isn’t one, Copilot can generate a fix based on the comment and surrounding code, so you can evaluate and test it right away.
Approve, complete, and merge
When you’re ready to decide, you can see the information you need and act without leaving the review. On the Overview tab, you can see status checks, merge conflicts, and whether any required approvals are still missing. You can approve the pull request from the diff view, with additional vote options for Azure DevOps pull requests.
You can also complete or merge the pull request right in the IDE. If plans change, you can convert it to draft or close it. Once you open the pull request, you can get all the way through the review in one place.
Try pull request review in 18.7
This is a big step forward for pull request review in Visual Studio, but we’re not done. We’re still working on features like comment filtering, a timeline of PR activity, and a smoother checkout flow for deeper review. We’re also keeping a close eye on feedback to figure out what’s next.
The pull request review experience is now available in the June 18.7 stable release. Try it out, and let us know what you want to see next on Developer Community or through our survey at aka.ms/ReviewPR.
Thanks to everyone who shared feedback and tried out pull request review in Insiders along the way. Your feedback helped shape the experience we’re shipping now.
Could we also integrate other repository servers like bitbucket , Gitlab etc for this code review feature or is it restricted to just GitHub at this moment
Could you tell me exactly how to do that?
When I connect to our DevOps Server 2022, my current Solution/git Repo closes and it looks like VS thinks I have on old tvfc Branch/Repo
it will be also a good idea to allow this context to copilot ,so he can review and help resolve the prs ,directly in vs.
right now the response is :
No. I cannot see the unresolved PR comments from Visual Studio in the current context.
I can only see the file/cache content that Visual Studio provided, but not the review conversation text or inline comment threads.
can you fix that ,it is very important.
@Leah Tran
When I check the VS 2026 18.7.0 release notes at the very top are:
- IDE (edit theme colors)
- Productivity(?!?) Color Emojis (?!?)
Seriously? Those are two most important things in the update? What the emojis have to do with productivity? Do developers now really use pictograms instead of words in code comments and filenames? Oh right, maybe productivity comes from reducing all error messages to ":( something happened"?
I know it's not your fault and yes I am ranting, but you guys should at least sort the release notes sections alphabetically so that C++, Git tooling, Github Copilot...
Works for on-prem azure DevOps also?
It’s worked for me with Azure DevOps Server 2022 [On Premise] after I connect to the repos from Team Explorer.
In the menu ‘Git’, I have the submenu ‘Azure DevOps’.
Yes, on-prem ADO should also be supported.
If you run into any issues getting it working, check out this reply on Developer Community for some troubleshooting steps. Please report issues on Developer Community if it isn’t working as expected so our engineers can follow up!
@Leah Tran, for me it’s not working for on-prem ADO, I don’t see a PR button in any of the mentioned windows.
Br
This is a good first step but only works in cases where the team is working in a single repo. In our case we have many repos with changes occurring across them all over the course of a sprint. We get notified via an email when a PR occurs. Clicking the link goes directly to the PR in the browser. That is a 1-click solution. I'm not sure how VS is going to improve upon that.
1. Email comes in for PR
2. Have to look at PR details to see if it applies to repo I'm currently working in
3....
Thanks for this feedback Michael! The multi-repo workflow you described is a good example of where there are still opportunities to improve the experience. The team has been actively discussing a better flow to open PRs in the IDE from external sources like email and browser. I’ve opened a suggestion on Developer Community to track this and share updates as the work progresses: https://developercommunity.visualstudio.com/t/Pull-Requests:-Add-Open-in-Visual-Studi/11106002