Merge pull request #13327 from Mikejo5000/mikejo-br25

Add instructions for showing file-level indicators for CodeLens

Author: prmerger-automator[bot]

docs/ide/find-code-changes-and-other-history-with-codelens.md

@@ -75,10 +75,12 @@ You can also view the file-level indicators for an entire file.
 > [!NOTE]
 > File-level indicators are not available for C# and Visual Basic files.
 
-To get more details about a change, right-click the item. Depending on whether you're using TFVC or Git, there are options to compare the versions of the file, view details and track the changeset, get the selected version of the file, and email the author of that change. Some of these details appear in **Team Explorer** if you have it enabled; otherwise, these details appear in **Git Changes**.
+To get more details about a change, right-click the item. Depending on whether you're using TFVC or Git, there are options to compare the versions of the file, view details and track the changeset, get the selected version of the file, and email the author of that change. Some of these details appear in **Team Explorer** if you have it enabled; otherwise, these details appear in **Git Changes** tab, and might also appear on the horizontal scrollbar at the bottom of the editor.
 
 You can also see who changed your code over time, which can help you find patterns in your team's changes and assess their impact.
 
+Starting in Visual Studio 2022 version 17.12 Preview 2, you can show or hide file-level indicators on the editor's horizontal scrollbar. To hide the indicators, open **Tools > Options > Text Editor > Advanced**, and then disable the **Show file level CodeLens indicator** option. This option affects visibility for file types that have the file-level CodeLens control in the bottom editor scrollbar such as XAML, HTML, and CSS, and does not affect files that contain inline CodeLens.
+
 ### Find changes in your current branch
 
 Your team might have multiple branches, for example a main branch and a child development branch, to reduce the risk of breaking stable code. You can find out how many people changed your code and how many changes were made in the main branch by pressing **Alt**+**6**.