From 2398f9adcd6767b615e204f6087fb939adbf9a2e Mon Sep 17 00:00:00 2001 From: Tomas Grosup Date: Thu, 20 Nov 2025 16:02:01 +0100 Subject: [PATCH 1/5] Update copilot-instructions with executable guidelines Added instructions for encapsulating code in standalone executables and including PR commentary. --- .github/copilot-instructions.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index e3a5e7f6ad9cf..448926088f159 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -44,6 +44,7 @@ For snippets >6 lines: 1. All code should use the latest stable versions/features. 1. Create examples in both C# and Visual Basic unless the article referencing the snippet resides in the in the `csharp`, `fsharp`, and `visual-basic` language folders. 1. When you add code, use code comments sparingly because they don't get localized. You can use them to briefly clarify code-specific details (such as logic, parameters, or edge cases). Put any critical information and context in the markdown text of the referencing article. +1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet rune myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code samples and proving what it has produced - can be diagnotics, standard output or a result value. ## File Naming @@ -69,4 +70,4 @@ When assigned an issue or directly given a task in GitHub: 3. Check for build warnings in the OpenPublishing.Build status check 4. If warnings exist: - Click "View Details" to open the build report - - Resolve any build warnings you introduced \ No newline at end of file + - Resolve any build warnings you introduced From c9cda639de23a26c33e52c23d5b148e1e59aa35f Mon Sep 17 00:00:00 2001 From: Tomas Grosup Date: Thu, 20 Nov 2025 16:05:11 +0100 Subject: [PATCH 2/5] Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 448926088f159..f6e0b880d81e6 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -44,7 +44,7 @@ For snippets >6 lines: 1. All code should use the latest stable versions/features. 1. Create examples in both C# and Visual Basic unless the article referencing the snippet resides in the in the `csharp`, `fsharp`, and `visual-basic` language folders. 1. When you add code, use code comments sparingly because they don't get localized. You can use them to briefly clarify code-specific details (such as logic, parameters, or edge cases). Put any critical information and context in the markdown text of the referencing article. -1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet rune myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code samples and proving what it has produced - can be diagnotics, standard output or a result value. +1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet rune myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code samples and proving what it has produced - can be diagnostics, standard output or a result value. ## File Naming From 18206e3e4a4fb7a6dccc0b3dab8e1bba668f9c27 Mon Sep 17 00:00:00 2001 From: Tomas Grosup Date: Thu, 20 Nov 2025 16:06:34 +0100 Subject: [PATCH 3/5] Apply suggestion from @T-Gro --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index f6e0b880d81e6..13677d66cfbbf 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -44,7 +44,7 @@ For snippets >6 lines: 1. All code should use the latest stable versions/features. 1. Create examples in both C# and Visual Basic unless the article referencing the snippet resides in the in the `csharp`, `fsharp`, and `visual-basic` language folders. 1. When you add code, use code comments sparingly because they don't get localized. You can use them to briefly clarify code-specific details (such as logic, parameters, or edge cases). Put any critical information and context in the markdown text of the referencing article. -1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet rune myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code samples and proving what it has produced - can be diagnostics, standard output or a result value. +1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet rune myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code samples and proving what it has produced - can be diagnostics, standard output or a result value. That standalone file is just for the purpose of verification within copilots execution environment, the published docs snippet should remain a subset as you would normally write to maximize clarity. ## File Naming From e52bebdbec423584569b9fc9d041eddb7faf5365 Mon Sep 17 00:00:00 2001 From: Bill Wagner Date: Thu, 20 Nov 2025 11:00:27 -0500 Subject: [PATCH 4/5] Update .github/copilot-instructions.md --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 13677d66cfbbf..6431cf6e3f88f 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -44,7 +44,7 @@ For snippets >6 lines: 1. All code should use the latest stable versions/features. 1. Create examples in both C# and Visual Basic unless the article referencing the snippet resides in the in the `csharp`, `fsharp`, and `visual-basic` language folders. 1. When you add code, use code comments sparingly because they don't get localized. You can use them to briefly clarify code-specific details (such as logic, parameters, or edge cases). Put any critical information and context in the markdown text of the referencing article. -1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet rune myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code samples and proving what it has produced - can be diagnostics, standard output or a result value. That standalone file is just for the purpose of verification within copilots execution environment, the published docs snippet should remain a subset as you would normally write to maximize clarity. +1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet run myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code samples and proving what it has produced - can be diagnostics, standard output or a result value. That standalone file is just for the purpose of verification within copilots execution environment, the published docs snippet should remain a subset as you would normally write to maximize clarity. ## File Naming From 7038d2e8099400b5e219c8a8382294eac2a946b9 Mon Sep 17 00:00:00 2001 From: Bill Wagner Date: Thu, 20 Nov 2025 11:08:27 -0500 Subject: [PATCH 5/5] Apply suggestions from code review --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 6431cf6e3f88f..7c3fa1b632662 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -44,7 +44,7 @@ For snippets >6 lines: 1. All code should use the latest stable versions/features. 1. Create examples in both C# and Visual Basic unless the article referencing the snippet resides in the in the `csharp`, `fsharp`, and `visual-basic` language folders. 1. When you add code, use code comments sparingly because they don't get localized. You can use them to briefly clarify code-specific details (such as logic, parameters, or edge cases). Put any critical information and context in the markdown text of the referencing article. -1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet run myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code samples and proving what it has produced - can be diagnostics, standard output or a result value. That standalone file is just for the purpose of verification within copilots execution environment, the published docs snippet should remain a subset as you would normally write to maximize clarity. +1. IMPORTANT: For created code, always try to encapsulate it in an standalone executable (e.g. `dotnet fsi myFile.fsx` or `dotnet run myFile.cs`, add the necessary boilerplate/imports/usings where needed, and execute it.). Run it, and for every code snippet, include a PR commentary checking each code sample and proving what it has produced - this can be diagnostics, standard output, or a result value. That standalone file is just for the purpose of verification within copilot's execution environment, the published docs snippet should remain a subset as you would normally write to maximize clarity. ## File Naming