[ci-scan-feedback] Add fixer freshness/live-leg gate to stop already-fixed & retired-leg PRs - #132318
Draft
kotlarmilos with Copilot wants to merge 2 commits into
Draft
[ci-scan-feedback] Add fixer freshness/live-leg gate to stop already-fixed & retired-leg PRs#132318kotlarmilos with Copilot wants to merge 2 commits into
kotlarmilos with Copilot wants to merge 2 commits into
Conversation
|
Azure Pipelines: 16 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Co-authored-by: kotlarmilos <11523312+kotlarmilos@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add fixer freshness/live-leg gate to stop already-fixed and retired-leg PRs
[ci-scan-feedback] Add fixer freshness/live-leg gate to stop already-fixed & retired-leg PRs
Aug 14, 2026
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
ci-failure-fixworkflow keeps opening help-wanted PRs for failures that no longer happen — retired legs (#129653, "Mono mobile doesn't run on CI anymore"), already-merged fixes (#130231), and stale KBEs (#130232). This is the dominant closed-unmerged class over the last several ticks, and prior feedback issues (#131644, #131699) flagged it without a guard ever landing.Changes
.github/workflows/ci-failure-fix.mdonly — prompt text, no code:skipped: no occurrence in last 14d, likely already fixed or retiredeng/pipelines/**atHEAD; retired Mono-mobile/wasm legs, deleted queues, dropped images →skipped: failing leg retired, no longer runs at HEADHEADplusgit logsince KBE creation; faulty path already removed →skipped: fix already present at HEAD; KBE stale.mdand MD009 is the sole enabled rule.Placement is deliberate: after Step 3 dedup, before Step 5's fix attempt, mirroring the existing Step 5.1.1 pipeline-category gate.
Recorded skipis already a valid outcome in the Step-summary table, so no downstream change is needed.Notes
No lock-file regeneration:
ci-failure-fix.lock.ymlpulls the prompt via{{#runtime-import .github/workflows/ci-failure-fix.md}}and stores no hash of the body — only frontmatter changes require a recompile, and the frontmatter is untouched. No other prompt references Step 4 items by number, so the renumbering is contained.Verified
markdownlint-cliclean on the file. Nothing built or tested — there is no code here.