[MS] Enhance Pull Request Reviews with In-Depth Feedback - devamazonaws.blogspot.com

Visual Studio 2022 has taken the pull request experience to the next level by making reviews interactive. We previously enabled viewing your pull request comments inline in your working files. Now, the latest update empowers you to add comments directly within the IDE, streamlining the review process. Now, pull request reviewers can conduct deep reviews with the navigational power of the IDE and stay in their focused environment. We heard from your feedback that the web experience for reviewing pull requests can only go so far. When you need to really understand your colleagues' proposed changes, it's best to checkout their branch and use the navigation and build tools in VS. Once you’re on their branch and you’ve identified some feedback, you can add the comment directly without having to map it back to the code in the web. This extends previous functionality where you could view and reply to only existing comments.

Enabling this feature

To start using the new commenting feature, first ensure you have enabled the feature flags:
  • Tools > Options > Preview Features > Pull Request Comments
  • Tools > Options > Pull Request Add Comment.
Once these are activated, checkout any branch with an active pull request and click on Show comments in files in the InfoBar to activate the pull request comments experience in the editor. Alternatively, you can enable comments by using the top level menu Git > ADO/GitHub > Show Comments in Files or from the PR dropdown menu next to the view all commits link in the Git Changes window. Git Changes window showing Branch has an active pull request. Show comments in files. Open in browser

Adding comments to pull request files

Simply click on the Add Comment icon in the margin, or right-click the line you'd like to comment on and select Git > Add Comment from the context menu. image hovering the add comment button The comment icon will only appear in files that are part of the pull request. For GitHub pull requests, comments can only be added to lines surrounding and including the changes.

We appreciate your feedback!

This is another step in our journey to deliver a powerful and integrated pull request experience. We started with supporting the create a pull request workflow, enabled viewing pull request comments on your checked out branches, and now, you can add new review comments, as well! We won’t stop there. Your continuous suggestions and insights play a crucial role in shaping the tools we build. We're thrilled to bring you this enhancement and are eager to hear how it improves your workflow.
Post Updated on March 20, 2025 at 03:00PM
Thanks for reading
from devamazonaws.blogspot.com

Comments

Post a Comment

Popular posts from this blog

[MS] Pulling a single item from a C++ parameter pack by its index, remarks - devamazonaws.blogspot.com

In my earlier discussion of pulling a single item from a C++ parameter pack by its index , I noted that with the Pack Indexing proposal, you would be able to write this to pull an item from a parameter pack while preserving its reference category. template<int index, typename...Args> void example(Args&&... args) { auto&& arg = (Args...[index]&&)args...[index]; using Arg = Args...[index]&&; } Why did I need to apply the (Args...[index]&&) cast ? Why can't I just write this: auto&& arg = args...[index]; or possibly decltype(auto) arg = args...[index]; Well, when you write the name of a variable, the result is an lvalue reference, even if the variable is an rvalue reference . Watch: struct S { S(S&); // construct from lvalue S(S&&); // construct from rvalue }; void whathappens(S&& s) { S t = s; // which will it use? } Try it out in your favorite compiler. This code construc...
Read more

[MS] Boosting Azure DevOps Security with GHAS Code Scanning - devamazonaws.blogspot.com

Image
Debjyoti Ganguly shares insights on the security benefits and configuration of GHAS Code Scanning with Azure DevOps. Boosting Azure DevOps Security with GHAS Code Scanning Code scanning, a pipeline-based tool available in GitHub Advanced Security, is designed to detect code vulnerabilities and bugs within the source code of ADO (Azure DevOps) repositories. Utilizing CodeQL as a static analysis tool, it performs query analysis and variant analysis. When vulnerabilities are found, it generates security alerts. CodeQL CodeQL is a powerful static analysis tool used for showing vulnerabilities and bugs in source code. It enables developers to write custom queries that analyze codebases, searching for specific patterns and potential security issues. By converting code into a database format, CodeQL allows for sophisticated, database-like queries to detect flaws. CodeQL in Action 1. Preparing the Code Create a CodeQL Database : Extract and structure the code into a database for analy...
Read more

[MS] Going beyond the empty set: Embracing the power of other empty things - devamazonaws.blogspot.com

The empty set contains nothing. This sounds really silly, but it's actually really nice. The Windows Runtime has a policy that if a method returns a collection (such as an IVector ), and the method produces no results, then it should return an empty collection, rather than a null reference . That way, consumers can just iterate over the collection without having to deal with a null test. For example, suppose you have a method Widget:: Get­Associated­Doodads which returns an IVectorView<Doodad> representing the Doodad objects that have been associated with a Widget object. If no Doodad s have been associated with the Widget , then it should return an empty vector, not a null pointer. That allows developers to write the natural-looking code: // C# foreach (var doodad in widget.GetAssociatedDoodads()) { ⟦ process each doodad ⟧ } // C++/WinRT for (auto&& doodad : widget.GetAssociatedDoodads()) { ⟦ process each doodad ⟧ } // JavaScript widget.GetAssociated...
Read more