From 3a3b9cc1911d9dfd70b5b710a6e40a20b65c09c3 Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Thu, 5 Feb 2026 10:05:13 -0800 Subject: [PATCH 1/2] Eliminate duplicate content and provide a clickable link (#36743) * Enhance issue triage report guidelines Added instructions for report file linking and content duplication. * Eliminate duplicate report content instruction Removed unnecessary instruction about providing a clickable link to the report file. --- .github/agents/issue-triage-nonblazor.agent.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/agents/issue-triage-nonblazor.agent.md b/.github/agents/issue-triage-nonblazor.agent.md index f6b0a02c5e08..4078b5fd55f0 100644 --- a/.github/agents/issue-triage-nonblazor.agent.md +++ b/.github/agents/issue-triage-nonblazor.agent.md @@ -67,7 +67,10 @@ If any content is not in English: ### File Naming `-analysis-report.md` +Provide a link to the report file, an absolute link that can be clicked on from anywhere. + ### Report Structure +Eliminate duplicate report content that may arise from running the analysis more than one time on an issue. #### Header (REQUIRED - Always include this community-facing notice) ```markdown From 59a3c7effb98c3141b999e9f42132db9d9a04808 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Thu, 5 Feb 2026 14:03:05 -0500 Subject: [PATCH 2/2] Clarify authentication context management in Blazor (#36745) --- aspnetcore/blazor/security/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/blazor/security/index.md b/aspnetcore/blazor/security/index.md index eec3fd2231e0..9c5d0408e526 100644 --- a/aspnetcore/blazor/security/index.md +++ b/aspnetcore/blazor/security/index.md @@ -92,7 +92,7 @@ For more information, see the following resources: Server-side Blazor apps are configured for security in the same manner as ASP.NET Core apps. For more information, see the articles under . -The authentication context is only established when the app starts, which is when the app first [connects to the WebSocket over a SignalR connection](xref:signalr/authn-and-authz) with the client. Authentication can be based on a cookie or some other bearer token, but authentication is managed via the SignalR hub and entirely within the [circuit](xref:blazor/hosting-models#blazor-server). The authentication context is maintained for the lifetime of the circuit. Apps periodically revalidate the user's authentication state every 30 minutes. +The authentication context is only established when the app starts, which is when the app first [connects to the WebSocket over a SignalR connection](xref:signalr/authn-and-authz) with the client. Authentication can be based on a cookie or some other bearer token, but authentication is managed via the SignalR hub and entirely within the [circuit](xref:blazor/hosting-models#blazor-server). The authentication context is maintained for the lifetime of the connection and is re-evaluated on reconnection. If the app must capture users for custom services or react to updates to the user, see .