Merged main into live

Author: mijacobs

docs/version-control/git-create-pull-request.md

@@ -2,7 +2,7 @@
 title: Create a pull request in Visual Studio
 titleSuffix: ""
 description: Create a pull request in Visual Studio by using GitHub or Azure DevOps.
-ms.date: 1/7/2025
+ms.date: 1/13/2025
 ms.topic: how-to
 author: ghogen
 ms.author: ghogen
@@ -61,18 +61,42 @@ To create a pull request, follow these steps:
 
 With Visual Studio 17.12 and later, you can enable the **Pull Request Templates** feature (in **Tools** > **Options** > **Environment** > **Preview Features**) so that your default PR template in your repo will be used when creating a new pull request for both GitHub and Azure DevOps. Learn more about how to add a pull request template to your repository in the [GitHub documentation](https://docs.github.com/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository) and [Azure DevOps documentation](/azure/devops/repos/git/pull-request-templates#default-pull-request-templates).
 
-## View pull request comments in the editor
+## View or add pull request comments in the editor
 
-As of Visual Studio 17.11, you can view comments and suggestions from reviewers without switching contexts to the browser.
+With Visual Studio 17.11 or later, you can view comments and suggestions from reviewers without switching contexts to the browser.
 
 ![Screenshot showing PR comments.](./media/vs-2022/git-pull-request-comments.png)
 
 To enable this feature, open **Tools** > **Options** > **Preview features** and make sure that **Pull Request Comments** is selected.
 
+### View pull request comments
+
 To view the comments for a pull request, check out any branch with an active pull request branch and select **Show comments in files** from the infobar. You can also select the PR number in the **Git Changes** window or from the Git top level menu with **Git** > **GitHub** or **Azure DevOps** > **Show comments in files**.
 
 ![Screenshot showing link to view comments in Git Changes window.](./media/vs-2022/git-pull-request-link-and-PR-number.png)
 
+### Add pull request comments
+
+With Visual Studio 17.13 or later, you can review a pull request, or add comments.
+
+To enable this feature, open **Tools** > **Options** > **Preview features** and make sure that **Pull Request Comments** is selected. Once these are activated, checkout any branch with an active pull request and click on **Show comments in files** in the infobar, and navigate through the changes using the toolbar buttons above the code file.
+
+To add a comment, click on the **Add comment** icon to the left side of the editor, as shown in the following screenshot.
+
+![Screenshot showing the Add comment icon when reviewing a file change in a pull request.](./media/vs-2022/pull-request-add-comment.png)
+
+You can also right-click on a line of code and, on the context menu, choose **Git** > **Add comment**.
+
+The comment text is not published until you click the **Add Comment** button on the comment window.
+
+You can continue the conversation on an existing comment by using the **Reply** section in the comment box. Comments are either active or resolved. You can click **Reply and Resolve** to reply to a comment and change the status to resolved in one click, or change the status using the dropdown above the comment text.
+
+You can toggle your like status on a comment by clicking on the icon, or by clicking on the three dots, you can copy the comment text to the clipboard, copy a link to the comment to the clipboard, delete the comment, or open the comment in the web browser at the provider's site (such as github.com or your Azure DevOps project site).
+
+The ability to add comments to a pull request is limited for some Git providers. For example, with GitHub as the provider, you can only add comments on lines within 3 lines of a change, but with the Azure DevOps provider, you can add comments at any line of a file involved in the pull request. In any case, you can only add comments on files that are included in the pull request.
+
+### Use the keyboard
+
 You can navigate across files and individual comments using the icons in the toolbar, or use the following keyboard shortcuts:
 
 | Action | Keyboard shortcut |
@@ -81,6 +105,7 @@ You can navigate across files and individual comments using the icons in the too
 | Go to the next file in the pull request | **Ctrl**+**Alt**+**F6** |
 | Go to the previous comment | **Ctrl**+**Shift**+**Alt**+**F8** |
 | Go to the next comment | **Ctrl**+**Alt**+**F8** |
+| Hide comments in files | **Ctrl**+**Shift**+**F1** |
 
 ## Next steps
 

docs/version-control/git-make-commit.md

@@ -40,9 +40,26 @@ Visual Studio also makes it easy to commit and sync with one click by using the
 
 :::image type="content" source="media/vs-2022/git-file-version-compare.png" alt-text="The line-by-line comparison of file versions in Visual Studio 2022.":::
 
+:::moniker range=">=vs-2022"
+
 New in [**version 17.6**](/visualstudio/releases/2022/release-notes-v17.6): You can also reference an issue or a pull request by typing `#` or selecting the **#** button in the lower right side of the commit message text box. For more information, see the [Reference issues and pull requests](https://devblogs.microsoft.com/visualstudio/reference-github-issues-and-pull-requests-in-visual-studio/) blog post.
 
-New in **version 17.12**: When you rename a file, you'll see a notification bar at the top of the **Git Changes** window informing you that a file was renamed, and prompting you to stage that change. This notification appears before you stage or commit anything. You might want to stage and commit the change before making other changes, in order to ensure that Git detects the change as a rename, not a deletion and addition of a new file.
+New in [**version 17.12**](/visualstudio/releases/2022/release-notes-v17.12): When you rename a file, you'll see a notification bar at the top of the **Git Changes** window informing you that a file was renamed, and prompting you to stage that change. This notification appears before you stage or commit anything. You might want to stage and commit the change before making other changes, in order to ensure that Git detects the change as a rename, not a deletion and addition of a new file.
+
+New in **version 17.13**: With [GitHub Copilot](../ide/visual-studio-github-copilot-install-and-states.md) installed, you can have GitHub Copilot review your code changes before you commit them. To use this feature, make sure that **Tools** > **Options** > **Preview Features** > **Pull Request Comments** is enabled, and also enable **Tools** > **Options** > **GitHub** > **Copilot** > **Source Control Integration** > **Enable Git preview features**.
+
+In the **Git Changes** window, click on the **Review changes with Copilot** button, which looks like a comment icon with a sparkle.
+
+After a few moments, a link showing the number of code review comments appears in the **Git Changes** window that you can click on to view and navigate the comments. If no issues are detected, the message **Copilot did not comment on any files** appears.
+
+![Screenshot showing Git Changes window with Review changes button.](./media/vs-2022/git-code-review-changes-button.png)
+
+The code review feedback shows up as comments, which show brief summary of the potential problem, and you can decide to make a change, or dismiss the comment box by using the downward arrow button on the top right of the comment box.
+
+![Screenshot showing GitHub code review comment.](./media/vs-2022/git-code-review-comment.png)
+
+To remove all comments, use the **X** in the Git Changes window to close the Copilot code review link.
+:::moniker-end
 
 ## Revert, reset, or amend a commit