Update skip_reason to clarify cancelled leg scenario by Copilot · Pull Request #127479 · dotnet/runtime

Copilot · 2026-04-27T23:11:38Z

Description

Improves the skip_reason message set on pipelines with zero test results to hint at the most common root cause: a cancelled leg.

Changes

extract_failed_tests.py: Updated skip_reason string from 'Build failed but no test failures detected via Test Results API' to 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg'

Original prompt

Update the skip_reason string on line 267 of .github/skills/ci-pipeline-monitor/scripts/extract_failed_tests.py in the dotnet/runtime repository.
Change the existing string from:
Build failed but no test failures detected via Test Results API
to the exact string:
Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg
The line currently reads:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API' WHERE name = ?",
After the change, it should read:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg' WHERE name = ?",
Only this single line needs to be modified. Do not change any other occurrences or files unless an identical duplicate of this exact string exists elsewhere in the same script and clearly needs to be kept consistent.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: File a PR to change this line to set skip_reason to Build failed but no test failures detected via Test Results API, e.g., due to a
cancelled leg.
Assistant: Waiting for your response to the dialog before proceeding with creating the pull request.
User: @copilot Dismissed Confirmation: Confirm agent session
Assistant: Understood — I won't create the PR. Let me know if you'd like me to proceed with it later.
User: It should be exact string "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg"
Assistant: I've started a coding agent session to open the PR updating the skip_reason string to "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg".

This pull request was created from Copilot chat.

Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

dotnet-policy-service · 2026-04-27T23:15:57Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

JulieLeeMSFT · 2026-04-29T18:47:24Z

@dhartglassMSFT PTAL.

Copilot

Pull request overview

This PR clarifies the skip_reason stored for pipelines that have a failed build result but return zero failed tests from the AzDO Test Results API, by explicitly calling out a common root cause (a cancelled leg). This improves downstream triage and reporting by making the “inconclusive” classification more actionable.

Changes:

Updated the skip_reason text used when marking zero-test-result pipelines as inconclusive to include “e.g., due to a cancelled leg”.

Copilot · 2026-04-27T23:11:38Z

Description

Improves the skip_reason message set on pipelines with zero test results to hint at the most common root cause: a cancelled leg.

Changes

extract_failed_tests.py: Updated skip_reason string from 'Build failed but no test failures detected via Test Results API' to 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg'

Original prompt

Update the skip_reason string on line 267 of .github/skills/ci-pipeline-monitor/scripts/extract_failed_tests.py in the dotnet/runtime repository.
Change the existing string from:
Build failed but no test failures detected via Test Results API
to the exact string:
Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg
The line currently reads:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API' WHERE name = ?",
After the change, it should read:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg' WHERE name = ?",
Only this single line needs to be modified. Do not change any other occurrences or files unless an identical duplicate of this exact string exists elsewhere in the same script and clearly needs to be kept consistent.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: File a PR to change this line to set skip_reason to Build failed but no test failures detected via Test Results API, e.g., due to a
cancelled leg.
Assistant: Waiting for your response to the dialog before proceeding with creating the pull request.
User: @copilot Dismissed Confirmation: Confirm agent session
Assistant: Understood — I won't create the PR. Let me know if you'd like me to proceed with it later.
User: It should be exact string "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg"
Assistant: I've started a coding agent session to open the PR updating the skip_reason string to "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg".

This pull request was created from Copilot chat.

Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

dotnet-policy-service · 2026-04-27T23:15:57Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

JulieLeeMSFT · 2026-04-29T18:47:24Z

@dhartglassMSFT PTAL.

Copilot

Pull request overview

This PR clarifies the skip_reason stored for pipelines that have a failed build result but return zero failed tests from the AzDO Test Results API, by explicitly calling out a common root cause (a cancelled leg). This improves downstream triage and reporting by making the “inconclusive” classification more actionable.

Changes:

Updated the skip_reason text used when marking zero-test-result pipelines as inconclusive to include “e.g., due to a cancelled leg”.

Copilot · 2026-04-27T23:11:38Z

Description

Improves the skip_reason message set on pipelines with zero test results to hint at the most common root cause: a cancelled leg.

Changes

extract_failed_tests.py: Updated skip_reason string from 'Build failed but no test failures detected via Test Results API' to 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg'

Original prompt

Update the skip_reason string on line 267 of .github/skills/ci-pipeline-monitor/scripts/extract_failed_tests.py in the dotnet/runtime repository.
Change the existing string from:
Build failed but no test failures detected via Test Results API
to the exact string:
Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg
The line currently reads:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API' WHERE name = ?",
After the change, it should read:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg' WHERE name = ?",
Only this single line needs to be modified. Do not change any other occurrences or files unless an identical duplicate of this exact string exists elsewhere in the same script and clearly needs to be kept consistent.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: File a PR to change this line to set skip_reason to Build failed but no test failures detected via Test Results API, e.g., due to a
cancelled leg.
Assistant: Waiting for your response to the dialog before proceeding with creating the pull request.
User: @copilot Dismissed Confirmation: Confirm agent session
Assistant: Understood — I won't create the PR. Let me know if you'd like me to proceed with it later.
User: It should be exact string "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg"
Assistant: I've started a coding agent session to open the PR updating the skip_reason string to "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg".

This pull request was created from Copilot chat.

Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

dotnet-policy-service · 2026-04-27T23:15:57Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

JulieLeeMSFT · 2026-04-29T18:47:24Z

@dhartglassMSFT PTAL.

Copilot

Pull request overview

This PR clarifies the skip_reason stored for pipelines that have a failed build result but return zero failed tests from the AzDO Test Results API, by explicitly calling out a common root cause (a cancelled leg). This improves downstream triage and reporting by making the “inconclusive” classification more actionable.

Changes:

Updated the skip_reason text used when marking zero-test-result pipelines as inconclusive to include “e.g., due to a cancelled leg”.

Copilot · 2026-04-27T23:11:38Z

Description

Improves the skip_reason message set on pipelines with zero test results to hint at the most common root cause: a cancelled leg.

Changes

extract_failed_tests.py: Updated skip_reason string from 'Build failed but no test failures detected via Test Results API' to 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg'

Original prompt

Update the skip_reason string on line 267 of .github/skills/ci-pipeline-monitor/scripts/extract_failed_tests.py in the dotnet/runtime repository.
Change the existing string from:
Build failed but no test failures detected via Test Results API
to the exact string:
Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg
The line currently reads:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API' WHERE name = ?",
After the change, it should read:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg' WHERE name = ?",
Only this single line needs to be modified. Do not change any other occurrences or files unless an identical duplicate of this exact string exists elsewhere in the same script and clearly needs to be kept consistent.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: File a PR to change this line to set skip_reason to Build failed but no test failures detected via Test Results API, e.g., due to a
cancelled leg.
Assistant: Waiting for your response to the dialog before proceeding with creating the pull request.
User: @copilot Dismissed Confirmation: Confirm agent session
Assistant: Understood — I won't create the PR. Let me know if you'd like me to proceed with it later.
User: It should be exact string "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg"
Assistant: I've started a coding agent session to open the PR updating the skip_reason string to "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg".

This pull request was created from Copilot chat.

Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

dotnet-policy-service · 2026-04-27T23:15:57Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

JulieLeeMSFT · 2026-04-29T18:47:24Z

@dhartglassMSFT PTAL.

Copilot

Pull request overview

This PR clarifies the skip_reason stored for pipelines that have a failed build result but return zero failed tests from the AzDO Test Results API, by explicitly calling out a common root cause (a cancelled leg). This improves downstream triage and reporting by making the “inconclusive” classification more actionable.

Changes:

Updated the skip_reason text used when marking zero-test-result pipelines as inconclusive to include “e.g., due to a cancelled leg”.

Copilot · 2026-04-27T23:11:38Z

Description

Improves the skip_reason message set on pipelines with zero test results to hint at the most common root cause: a cancelled leg.

Changes

extract_failed_tests.py: Updated skip_reason string from 'Build failed but no test failures detected via Test Results API' to 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg'

Original prompt

Update the skip_reason string on line 267 of .github/skills/ci-pipeline-monitor/scripts/extract_failed_tests.py in the dotnet/runtime repository.
Change the existing string from:
Build failed but no test failures detected via Test Results API
to the exact string:
Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg
The line currently reads:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API' WHERE name = ?",
After the change, it should read:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg' WHERE name = ?",
Only this single line needs to be modified. Do not change any other occurrences or files unless an identical duplicate of this exact string exists elsewhere in the same script and clearly needs to be kept consistent.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: File a PR to change this line to set skip_reason to Build failed but no test failures detected via Test Results API, e.g., due to a
cancelled leg.
Assistant: Waiting for your response to the dialog before proceeding with creating the pull request.
User: @copilot Dismissed Confirmation: Confirm agent session
Assistant: Understood — I won't create the PR. Let me know if you'd like me to proceed with it later.
User: It should be exact string "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg"
Assistant: I've started a coding agent session to open the PR updating the skip_reason string to "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg".

This pull request was created from Copilot chat.

Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

dotnet-policy-service · 2026-04-27T23:15:57Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

JulieLeeMSFT · 2026-04-29T18:47:24Z

@dhartglassMSFT PTAL.

Copilot

Pull request overview

This PR clarifies the skip_reason stored for pipelines that have a failed build result but return zero failed tests from the AzDO Test Results API, by explicitly calling out a common root cause (a cancelled leg). This improves downstream triage and reporting by making the “inconclusive” classification more actionable.

Changes:

Updated the skip_reason text used when marking zero-test-result pipelines as inconclusive to include “e.g., due to a cancelled leg”.

Copilot · 2026-04-27T23:11:38Z

Description

Improves the skip_reason message set on pipelines with zero test results to hint at the most common root cause: a cancelled leg.

Changes

extract_failed_tests.py: Updated skip_reason string from 'Build failed but no test failures detected via Test Results API' to 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg'

Original prompt

Update the skip_reason string on line 267 of .github/skills/ci-pipeline-monitor/scripts/extract_failed_tests.py in the dotnet/runtime repository.
Change the existing string from:
Build failed but no test failures detected via Test Results API
to the exact string:
Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg
The line currently reads:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API' WHERE name = ?",
After the change, it should read:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg' WHERE name = ?",
Only this single line needs to be modified. Do not change any other occurrences or files unless an identical duplicate of this exact string exists elsewhere in the same script and clearly needs to be kept consistent.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: File a PR to change this line to set skip_reason to Build failed but no test failures detected via Test Results API, e.g., due to a
cancelled leg.
Assistant: Waiting for your response to the dialog before proceeding with creating the pull request.
User: @copilot Dismissed Confirmation: Confirm agent session
Assistant: Understood — I won't create the PR. Let me know if you'd like me to proceed with it later.
User: It should be exact string "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg"
Assistant: I've started a coding agent session to open the PR updating the skip_reason string to "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg".

This pull request was created from Copilot chat.

Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

dotnet-policy-service · 2026-04-27T23:15:57Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

JulieLeeMSFT · 2026-04-29T18:47:24Z

@dhartglassMSFT PTAL.

Copilot

Pull request overview

This PR clarifies the skip_reason stored for pipelines that have a failed build result but return zero failed tests from the AzDO Test Results API, by explicitly calling out a common root cause (a cancelled leg). This improves downstream triage and reporting by making the “inconclusive” classification more actionable.

Changes:

Updated the skip_reason text used when marking zero-test-result pipelines as inconclusive to include “e.g., due to a cancelled leg”.

Copilot · 2026-04-27T23:11:38Z

Description

Improves the skip_reason message set on pipelines with zero test results to hint at the most common root cause: a cancelled leg.

Changes

extract_failed_tests.py: Updated skip_reason string from 'Build failed but no test failures detected via Test Results API' to 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg'

Original prompt

Update the skip_reason string on line 267 of .github/skills/ci-pipeline-monitor/scripts/extract_failed_tests.py in the dotnet/runtime repository.
Change the existing string from:
Build failed but no test failures detected via Test Results API
to the exact string:
Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg
The line currently reads:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API' WHERE name = ?",
After the change, it should read:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg' WHERE name = ?",
Only this single line needs to be modified. Do not change any other occurrences or files unless an identical duplicate of this exact string exists elsewhere in the same script and clearly needs to be kept consistent.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: File a PR to change this line to set skip_reason to Build failed but no test failures detected via Test Results API, e.g., due to a
cancelled leg.
Assistant: Waiting for your response to the dialog before proceeding with creating the pull request.
User: @copilot Dismissed Confirmation: Confirm agent session
Assistant: Understood — I won't create the PR. Let me know if you'd like me to proceed with it later.
User: It should be exact string "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg"
Assistant: I've started a coding agent session to open the PR updating the skip_reason string to "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg".

This pull request was created from Copilot chat.

Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

dotnet-policy-service · 2026-04-27T23:15:57Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

JulieLeeMSFT · 2026-04-29T18:47:24Z

@dhartglassMSFT PTAL.

Copilot

Pull request overview

This PR clarifies the skip_reason stored for pipelines that have a failed build result but return zero failed tests from the AzDO Test Results API, by explicitly calling out a common root cause (a cancelled leg). This improves downstream triage and reporting by making the “inconclusive” classification more actionable.

Changes:

Updated the skip_reason text used when marking zero-test-result pipelines as inconclusive to include “e.g., due to a cancelled leg”.

Copilot · 2026-04-27T23:11:38Z

Description

Improves the skip_reason message set on pipelines with zero test results to hint at the most common root cause: a cancelled leg.

Changes

extract_failed_tests.py: Updated skip_reason string from 'Build failed but no test failures detected via Test Results API' to 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg'

Original prompt

Update the skip_reason string on line 267 of .github/skills/ci-pipeline-monitor/scripts/extract_failed_tests.py in the dotnet/runtime repository.
Change the existing string from:
Build failed but no test failures detected via Test Results API
to the exact string:
Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg
The line currently reads:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API' WHERE name = ?",
After the change, it should read:
"UPDATE pipelines SET result = 'inconclusive', skip_reason = 'Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg' WHERE name = ?",
Only this single line needs to be modified. Do not change any other occurrences or files unless an identical duplicate of this exact string exists elsewhere in the same script and clearly needs to be kept consistent.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: File a PR to change this line to set skip_reason to Build failed but no test failures detected via Test Results API, e.g., due to a
cancelled leg.
Assistant: Waiting for your response to the dialog before proceeding with creating the pull request.
User: @copilot Dismissed Confirmation: Confirm agent session
Assistant: Understood — I won't create the PR. Let me know if you'd like me to proceed with it later.
User: It should be exact string "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg"
Assistant: I've started a coding agent session to open the PR updating the skip_reason string to "Build failed but no test failures detected via Test Results API, e.g., due to a cancelled leg".

This pull request was created from Copilot chat.

Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

dotnet-policy-service · 2026-04-27T23:15:57Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

JulieLeeMSFT · 2026-04-29T18:47:24Z

@dhartglassMSFT PTAL.

Copilot

Pull request overview

This PR clarifies the skip_reason stored for pipelines that have a failed build result but return zero failed tests from the AzDO Test Results API, by explicitly calling out a common root cause (a cancelled leg). This improves downstream triage and reporting by making the “inconclusive” classification more actionable.

Changes:

Updated the skip_reason text used when marking zero-test-result pipelines as inconclusive to include “e.g., due to a cancelled leg”.

Initial plan
22b0e33

CopilotAI assigned Copilot and JulieLeeMSFT Apr 27, 2026

CopilotAI requested review from Copilot and removed request for Copilot April 27, 2026 23:11

Copilotstarted work on behalf of JulieLeeMSFT April 27, 2026 23:11 View session

github-actionsBot added the area-Infrastructure label Apr 27, 2026

github-project-automationBot added this to Runtime Infra Apr 27, 2026

Update skip_reason to mention cancelled leg
3320c5a
Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/def4fe93-ca7b-46ea-9e72-1ff388f942c7 Co-authored-by: JulieLeeMSFT <63486087+JulieLeeMSFT@users.noreply.github.com>

CopilotAI requested review from Copilot and removed request for Copilot April 27, 2026 23:14

CopilotAI changed the title ~~[WIP] Update skip_reason string in extract_failed_tests.py~~Update skip_reason to clarify cancelled leg scenarioApr 27, 2026

CopilotAI requested a review from JulieLeeMSFT April 27, 2026 23:14

Copilotfinished work on behalf of JulieLeeMSFT April 27, 2026 23:16

JulieLeeMSFT approved these changes Apr 29, 2026
View reviewed changes

JulieLeeMSFT marked this pull request as ready for review April 29, 2026 18:46

CopilotAI review requested due to automatic review settings April 29, 2026 18:46

Copilotstarted reviewing on behalf of JulieLeeMSFT April 29, 2026 18:46 View session

JulieLeeMSFT added area-skills Agent Skills and removed area-Infrastructure labels Apr 29, 2026

CopilotAI reviewed Apr 29, 2026
View reviewed changes

dhartglassMSFT approved these changes Apr 29, 2026
View reviewed changes

JulieLeeMSFT merged commit 34c5058 into mainApr 30, 2026
27 checks passed

JulieLeeMSFT deleted the copilot/update-skip-reason-string branch April 30, 2026 16:44

github-project-automationBot moved this to Done in Runtime Infra Apr 30, 2026

dotnet-maestroBot mentioned this pull request May 1, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#6411
Merged

github-actionsBot locked and limited conversation to collaborators May 31, 2026