Skip to content

Commit 7917e3e

Browse files
Merge pull request #10346 from MicrosoftDocs/main638591942497985715sync_temp
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
2 parents f0eb57f + ac182ae commit 7917e3e

File tree

3 files changed

+16
-5
lines changed

3 files changed

+16
-5
lines changed
Loading

docs/debugger/using-breakpoints.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Use breakpoints in the debugger
33
description: Learn about breakpoints, one of the most important debugging techniques. The article covers breakpoint actions, tracepoints, conditions, and much more.
4-
ms.date: 12/06/2023
4+
ms.date: 08/13/2024
55
ms.topic: how-to
66
f1_keywords:
77
- vs.debug.breakpointswin
@@ -370,6 +370,19 @@ You can use labels to sort and filter the list of breakpoints in the **Breakpoin
370370
1. To add a label to a breakpoint, right-click the breakpoint in the source code or the **Breakpoints** window, and then select **Edit labels**. Add a new label or choose an existing one, and then select **OK**.
371371
2. Sort the breakpoint list in the **Breakpoints** window by selecting the **Labels**, **Conditions**, or other column headers. You can select the columns to display by selecting **Show Columns** in the toolbar.
372372

373+
::: moniker range=">= vs-2022"
374+
### Breakpoint groups
375+
376+
For complex debugging scenarios, you may want to create breakpoint groups to organize your breakpoints. This allows you to quickly enable and disable logical groupings of breakpoints, based upon the current scenario that you're trying to debug.
377+
378+
You can create breakpoints in the **Breakpoints** window by selecting **New > Breakpoint Group**, and providing a name for the group. To add a breakpoint to a group, right-click the breakpoint and choose **Add to Breakpoint Group** > **\<group name\>**. Or, drag-and-drop your breakpoints into the desired group.
379+
380+
![Screenshot of breakpoint groups.](../debugger/media/vs-2022/breakpoints-window-breakpoint-groups.png)
381+
382+
To set a default breakpoint group, right-click a group and select **Set as default Breakpoint Group**. When you set a default breakpoint group, newly created breakpoints are automatically added to the group.
383+
384+
::: moniker-end
385+
373386
### Export and import breakpoints
374387

375388
To save or share the state and location of your breakpoints, you can export or import them.

docs/version-control/git-browse-repository.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Browse repos, compare branches & commits"
33
description: Browse any Git repository in Visual Studio by using the Git Repository window to view local and remote branches and multiple branches at the same time.
4-
ms.date: 08/08/2023
4+
ms.date: 08/13/2024
55
ms.topic: how-to
66
author: ghogen
77
ms.author: ghogen
@@ -53,8 +53,6 @@ You can browse through any local or remote branch without having to switch your
5353

5454
There's both line coloring and branch labels on the left side of the **Local History** view that help make it easier to trace which commits belong to each branch. You can use the list of branches at the top of the table to scroll between branches more easily and know immediately which branches appear in the graph.
5555

56-
<a name="compare-commits"/>
57-
5856
## Compare commits
5957

6058
To compare any two commits in your branch, use the **Ctrl** key to select the two commits that you want to compare. Then, right-click one of them and select **Compare Commits**.
@@ -118,4 +116,4 @@ Checking out the tip of a remote branch can be helpful if you would like to quic
118116
## Related content
119117

120118
- [Manage Git repositories in Visual Studio](git-manage-repository.md)
121-
- [The Git experience in Visual Studio](git-with-visual-studio.md)
119+
- [The Git experience in Visual Studio](git-with-visual-studio.md)

0 commit comments

Comments
 (0)