Delete ML-based issue/PR labeler - #69019
Merged
Merged
Conversation
DeagleGross
approved these changes
Sep 3, 2026
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
.github/labeler.README.md still documents these deleted workflows as active and should be updated/removed to avoid stale guidance.
Pull request overview
Removes legacy ML-based GitHub Actions workflows that used dotnet/issue-labeler for issue/PR area-label prediction, aligning the repo with the newer deterministic/agentic labeling approach referenced in the PR description.
Changes:
- Deleted the workflow that trained ML models for label prediction.
- Deleted the workflow that promoted staged models to the active slot.
- Deleted scheduled/dispatch workflows that predicted labels and retained cached models.
File summaries
| File | Description |
|---|---|
| .github/workflows/labeler-train.yml | Removes the ML model training workflow. |
| .github/workflows/labeler-promote.yml | Removes the model promotion workflow. |
| .github/workflows/labeler-predict-pulls.yml | Removes the PR label prediction workflow (ML-based). |
| .github/workflows/labeler-predict-issues.yml | Removes the issue label prediction workflow (ML-based). |
| .github/workflows/labeler-cache-retention.yml | Removes the cache-retention workflow used to prevent model eviction. |
Review details
Suppressed comments (1)
.github/workflows/labeler-predict-issues.yml:1
- This workflow is being removed, but the repo documentation at
.github/labeler.README.mdstill describes thedotnet/issue-labelerworkflows (includinglabeler-predict-issues.yml) as active. Please update or remove that README as part of this cleanup so it doesn’t mislead contributors.
- Files reviewed: 5/5 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
wtgodbe
approved these changes
Sep 4, 2026
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.
Once we are happy with the workflow added in #69008 and the agentic workflow for labeling issue, these old ML-based workflows can be deleted.
These workflows have been broken for a while already, it seems.
FYI @jeffhandley