From 2716548f33d83dc7caf4a9fbbe3b87150a41349c Mon Sep 17 00:00:00 2001 From: Copilot <198982749+Copilot@users.noreply.github.com> Date: Thu, 29 Jan 2026 13:49:44 -0800 Subject: [PATCH 1/2] Remove non-functional AI triage workflow (#36712) * Initial plan * Remove non-functional AI triage workflow Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> * Remove orphaned agent configuration file Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> * Restore agent configuration file as requested Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> --- .../issue-processing-ai-triage-nonblazor.yml | 98 ------------------- 1 file changed, 98 deletions(-) delete mode 100644 .github/workflows/issue-processing-ai-triage-nonblazor.yml diff --git a/.github/workflows/issue-processing-ai-triage-nonblazor.yml b/.github/workflows/issue-processing-ai-triage-nonblazor.yml deleted file mode 100644 index a0074b9e84fc..000000000000 --- a/.github/workflows/issue-processing-ai-triage-nonblazor.yml +++ /dev/null @@ -1,98 +0,0 @@ -name: Issue Triage with Copilot - -# ============================================================================= -# TRIGGER CONFIGURATION -# This workflow runs automatically when a new issue is opened in the repository -# ============================================================================= -on: - issues: - types: - - opened - -jobs: - triage-non-blazor-issue: - # =========================================================================== - # JOB FILTER CONDITION - # Only run this job for issues that: - # 1. Reference ASP.NET Core documentation (must contain aspnetcore/ path) - # 2. Are NOT related to Blazor content (excludes blazor/ folder) - # 3. Are NOT related to Blazor-adjacent content (excludes specific - # client-side interop and component tag helper docs that are - # Blazor-related but located outside the blazor/ folder) - # =========================================================================== - if: | - contains(github.event.issue.body, 'https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/') - && !contains(github.event.issue.body, 'https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor') - && !contains(github.event.issue.body, 'https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/client-side/dotnet-interop/index.md') - && !contains(github.event.issue.body, 'https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/client-side/dotnet-interop/wasm-browser-app.md') - && !contains(github.event.issue.body, 'https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/client-side/dotnet-on-webworkers.md') - && !contains(github.event.issue.body, 'https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/mvc/views/tag-helpers/built-in/component-tag-helper.md') - && !contains(github.event.issue.body, 'https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/mvc/views/tag-helpers/built-in/persist-component-state.md') - runs-on: ubuntu-latest - - # =========================================================================== - # PERMISSIONS - # - issues: write - Required to post comments and add labels to issues - # - contents: read - Required to checkout the repository and read agent file - # - pull-requests: read - Required for Copilot action to access PR context that may be referred to in the issue. - # =========================================================================== - permissions: - issues: write - contents: read - pull-requests: read - steps: - # ========================================================================= - # STEP 1: POST WELCOME MESSAGE - # Immediately acknowledge the issue with a friendly welcome message - # to let the submitter know their issue has been received - # ========================================================================= - - name: Post welcome message - uses: actions/github-script@v6 - with: - script: | - await github.rest.issues.createComment({ - issue_number: context.issue.number, - owner: context.repo.owner, - repo: context.repo.repo, - body: `### 👋 ***Thanks for your issue!*** 😊\n\nWe will be along shortly to assist.` - }) - - # ========================================================================= - # STEP 2: CHECKOUT REPOSITORY - # Clone the repository to access the Copilot agent configuration file - # located at .github/agents/issue-triage-nonblazor.agent.md - # ========================================================================= - - name: Checkout repository - uses: actions/checkout@v4 - - # ========================================================================= - # STEP 3: RUN COPILOT AI TRIAGE - # Execute the Copilot action with the non-Blazor triage agent to: - # - Analyze the issue content - # - Generate a triage report with recommendations - # - Post the analysis as a comment on the issue - # ========================================================================= - - name: Run Copilot Issue Triage - uses: github/copilot-action@v1 - with: - agent: .github/agents/issue-triage-nonblazor.agent.md - prompt: | - Analyze issue #${{ github.event.issue.number }} and post your triage report as a comment on the issue. - Issue URL: ${{ github.event.issue.html_url }} - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - # ========================================================================= - # STEP 4: ADD TRIAGE LABEL - # Apply the "ai-triage-action-plan" label to indicate this issue has been - # processed by the AI triage workflow and has an action plan generated - # ========================================================================= - - name: Add triage label - uses: actions/github-script@v6 - with: - script: | - await github.rest.issues.addLabels({ - issue_number: context.issue.number, - owner: context.repo.owner, - repo: context.repo.repo, - labels: ["ai-triage-action-plan"] - }) From c1f0d177c954102ea2d23f963257d90c86997986 Mon Sep 17 00:00:00 2001 From: Copilot <198982749+Copilot@users.noreply.github.com> Date: Thu, 29 Jan 2026 15:52:01 -0800 Subject: [PATCH 2/2] Correct IMemoryPoolFactory documentation: custom factories don't inherit auto-eviction (#36716) * Initial plan * Fix IMemoryPoolFactory documentation - custom factories do not auto-evict Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> * Update related memory pool factory documentation in Kestrel and HTTP.sys docs Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> --- aspnetcore/fundamentals/servers/httpsys.md | 3 ++- aspnetcore/fundamentals/servers/includes/memory-eviction2.md | 2 +- aspnetcore/fundamentals/servers/kestrel/memory-management.md | 5 +++-- aspnetcore/release-notes/aspnetcore-10.0.md | 3 ++- .../release-notes/aspnetcore-10/includes/memory-eviction.md | 2 +- 5 files changed, 9 insertions(+), 6 deletions(-) diff --git a/aspnetcore/fundamentals/servers/httpsys.md b/aspnetcore/fundamentals/servers/httpsys.md index 8d138df7dd3e..daa7290ebc04 100644 --- a/aspnetcore/fundamentals/servers/httpsys.md +++ b/aspnetcore/fundamentals/servers/httpsys.md @@ -1,11 +1,12 @@ --- title: HTTP.sys web server implementation in ASP.NET Core +ai-usage: ai-assisted author: tdykstra description: Learn about HTTP.sys, a web server for ASP.NET Core on Windows. Built on the HTTP.sys kernel-mode driver, HTTP.sys is an alternative to Kestrel that can be used for direct connection to the Internet without IIS. monikerRange: '>= aspnetcore-2.1' ms.author: tdykstra ms.custom: mvc -ms.date: 08/04/2025 +ms.date: 01/29/2026 uid: fundamentals/servers/httpsys --- # HTTP.sys web server implementation in ASP.NET Core diff --git a/aspnetcore/fundamentals/servers/includes/memory-eviction2.md b/aspnetcore/fundamentals/servers/includes/memory-eviction2.md index 2f7645e11a8a..c2358185b6d4 100644 --- a/aspnetcore/fundamentals/servers/includes/memory-eviction2.md +++ b/aspnetcore/fundamentals/servers/includes/memory-eviction2.md @@ -18,7 +18,7 @@ The following code example shows a simple background service that uses the built :::code language="csharp" source="~/fundamentals/servers/snippets/10.x/my-background-service.cs"::: -To use a custom memory pool factory, make a class that implements `IMemoryPoolFactory` and register it with dependency injection, as the following example does. Memory pools created this way also benefit from the automatic eviction feature: +To use a custom memory pool factory, make a class that implements `IMemoryPoolFactory` and register it with dependency injection, as the following example does. Memory pools created this way do not benefit from the automatic eviction feature unless you implement similar eviction logic in your custom factory: :::code language="csharp" source="~/fundamentals/servers/snippets/10.x/memory-pool-factory.cs"::: diff --git a/aspnetcore/fundamentals/servers/kestrel/memory-management.md b/aspnetcore/fundamentals/servers/kestrel/memory-management.md index 2f8a788fd371..29fcdbc1020f 100644 --- a/aspnetcore/fundamentals/servers/kestrel/memory-management.md +++ b/aspnetcore/fundamentals/servers/kestrel/memory-management.md @@ -1,10 +1,11 @@ --- title: Memory management in Kestrel +ai-usage: ai-assisted author: tdykstra description: Learn about memory management in Kestrel, including automatic eviction from memory pools and using memory pool metrics. monikerRange: '>= aspnetcore-10.0' ms.author: tdykstra -ms.date: 12/04/2025 +ms.date: 01/29/2026 uid: fundamentals/servers/kestrel/memory-management --- @@ -34,7 +35,7 @@ The following code example shows a simple background service that uses the built :::code language="csharp" source="~/fundamentals/servers/snippets/10.x/my-background-service.cs"::: -To use a custom memory pool factory, make a class that implements `IMemoryPoolFactory` and register it with dependency injection, as the following example does. Memory pools created this way also benefit from the automatic eviction feature: +To use a custom memory pool factory, make a class that implements `IMemoryPoolFactory` and register it with dependency injection, as the following example does. Memory pools created this way do not benefit from the automatic eviction feature unless you implement similar eviction logic in your custom factory: :::code language="csharp" source="~/fundamentals/servers/snippets/10.x/memory-pool-factory.cs"::: diff --git a/aspnetcore/release-notes/aspnetcore-10.0.md b/aspnetcore/release-notes/aspnetcore-10.0.md index eae4de6c8e18..3224c2578a3a 100644 --- a/aspnetcore/release-notes/aspnetcore-10.0.md +++ b/aspnetcore/release-notes/aspnetcore-10.0.md @@ -1,10 +1,11 @@ --- title: What's new in ASP.NET Core in .NET 10 +ai-usage: ai-assisted author: wadepickett description: Learn about the new features in ASP.NET Core in .NET 10. ms.author: wpickett ms.custom: mvc -ms.date: 11/11/2025 +ms.date: 01/29/2026 uid: aspnetcore-10 --- # What's new in ASP.NET Core in .NET 10 diff --git a/aspnetcore/release-notes/aspnetcore-10/includes/memory-eviction.md b/aspnetcore/release-notes/aspnetcore-10/includes/memory-eviction.md index a00a418cfb08..77673a233b9e 100644 --- a/aspnetcore/release-notes/aspnetcore-10/includes/memory-eviction.md +++ b/aspnetcore/release-notes/aspnetcore-10/includes/memory-eviction.md @@ -48,7 +48,7 @@ public class MyBackgroundService : BackgroundService } ``` -To use your own memory pool factory, make a class that implements `IMemoryPoolFactory` and register it with dependency injection, as the following example does. Memory pools created this way also benefit from the automatic eviction feature: +To use your own memory pool factory, make a class that implements `IMemoryPoolFactory` and register it with dependency injection, as the following example does. Memory pools created this way do not benefit from the automatic eviction feature unless you implement similar eviction logic in your custom factory: ```csharp services.AddSingleton,