Repo sync for protected branch

.github/workflows/clean-repo.yml

@@ -39,7 +39,7 @@ jobs:
 
       # Create the PR for the work done by the "clean repo" tool
       - name: create-pull-request
-        uses: peter-evans/create-pull-request@8867c4aba1b742c39f8d0ba35429c2dfa4b6cb20
+        uses: peter-evans/create-pull-request@6cd32fd93684475c31847837f87bb135d40a2b79
         with:
           branch: create-cleanrepo-pull-request/patch
           title: "Monthly chores: Automated repo cleanup"

.github/workflows/whats-new.yml

@@ -41,7 +41,7 @@ jobs:
           savefile: './docs/ide/whats-new-visual-studio-docs.md'
 
       - name: create-pull-request
-        uses: peter-evans/create-pull-request@8867c4aba1b742c39f8d0ba35429c2dfa4b6cb20
+        uses: peter-evans/create-pull-request@6cd32fd93684475c31847837f87bb135d40a2b79
         with:
           branch: create-whatsnew-pull-request/patch
           title: "What's new article"

docs/containers/overview.md

@@ -1,6 +1,6 @@
 ---
-title: Visual Studio Container Tools & Docker on Windows
-description: Explore tools available for working with Docker containers in Visual Studio for Windows, including continuous delivery and continuous integration (CI/CD).
+title: Visual Studio Container Tools and Docker on Windows
+description: Explore tools available for working with Docker containers in Visual Studio for Windows, including CI/CD, and choose whether to work with a Dockerfile, or build a containerized app without a Dockerfile.
 author: ghogen
 ms.author: ghogen
 ms.topic: overview
@@ -190,7 +190,7 @@ COPY --from=publish /app/publish .
 ENTRYPOINT ["dotnet", "WebApplication-Docker.dll"]
 ```
 
-## Add Docker support using the .NET SDK option
+## Containerize a .NET app without a Dockerfile
 
 With Visual Studio 2022 17.9 and later with the .NET 7 SDK installed, in ASP.NET Core projects that target .NET 6 or later, you have the option of using .NET SDK's built-in support for container builds, which means you don't need a Dockerfile; see [Containerize a .NET app with dotnet publish](/dotnet/core/docker/publish-as-container?pivots=dotnet-8-0). Instead, you configure your containers using MSBuild properties in the project file, and the settings for launching the containers with Visual Studio are encoded in a `.json` configuration file, *launchSettings.json*.
 

docs/test/how-to-create-a-data-driven-unit-test.md

@@ -185,6 +185,9 @@ The `DataSource` attribute specifies the connection string for the data source a
 [DataSource(@"Provider=Microsoft.SqlServerCe.Client.4.0;Data Source=C:\Data\MathsData.sdf", "AddIntegersData")]
 ```
 
+> [!CAUTION]
+> The connection string can contain sensitive data (for example, a password). The connection string is stored in plain text in source code and in the compiled assembly. Restrict access to the source code and assembly to protect this sensitive information.
+
 The DataSource attribute has three constructors.
 
 ```csharp

docs/test/microsoft-code-coverage-console-tool.md

@@ -7,6 +7,7 @@ ms.author: mikejo
 manager: mijacobs
 ms.subservice: test-tools
 author: mikejo5000
+monikerRange: '>= vs-2022'
 ---
 # Microsoft.CodeCoverage.Console tool
 
@@ -44,8 +45,7 @@ Commands:
 
 The Microsoft.CodeCoverage.Console tool is extension to the [dotnet-coverage](/dotnet/core/additional-tools/dotnet-coverage) dotnet tool. The documentation for collect, connect, shutdown, merge, and snapshot commands can be found [here](/dotnet/core/additional-tools/dotnet-coverage).
 
-::: moniker range=">=vs-2022"
-Starting in Visual Studio 2022, Microsoft.CodeCoverage.Console supports additional security features to enable collecting ASP.NET code coverage data from IIS. Additionally, the Microsoft.CodeCoverage.Console tool supports collecting code coverage for C++ code. The `instrument` command is specific to these scenarios.
+Microsoft.CodeCoverage.Console supports additional security features to enable collecting ASP.NET code coverage data from IIS. Additionally, the Microsoft.CodeCoverage.Console tool supports collecting code coverage for C++ code. The `instrument` command is specific to these scenarios.
 
 ## Instrument command
 
@@ -171,8 +171,6 @@ Finally, close the collector as follows:
 D:\ConsoleApplication\x64\Debug>Microsoft.CodeCoverage.Console shutdown 73c34ce5-501c-4369-a4cb-04d31427d1a4
 ```
 
-::: moniker-end
-
 ## Related content
 
 - [dotnet-coverage code coverage utility](/dotnet/core/additional-tools/dotnet-coverage)

docs/test/walkthrough-using-a-configuration-file-to-define-a-data-source.md

@@ -74,6 +74,9 @@ The **section** element should look similar to this:
 
 The connection strings define provider-specific information for accessing data sources. Connection strings defined in configuration files provide reusable data provider information across an application. In this section, you create two connection strings that will be used by data sources that are defined in the Custom Configuration Section.
 
+> [!CAUTION]
+> The connection string can contain sensitive data (for example, a password). The connection string is stored in plain text in source code and in the compiled assembly. Restrict access to the source code and assembly to protect this sensitive information.
+
 ### To define connection strings
 
 1. After the **configSections** element, create a **connectionStrings** element.