[issue-labeler] Use env var for prediction threshold; default to 0.05#124435
Merged
jeffhandley merged 2 commits intodotnet:mainfrom Feb 16, 2026
Merged
Conversation
…SSUE_LABELER_PREDICTION_THRESHOLD Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Tagging subscribers to this area: @dotnet/area-meta |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR makes the issue-labeler prediction threshold configurable and lowers the default from 0.40 to 0.05 based on evaluation of multiple training runs. The change aims to minimize occurrences of issues/PRs needing manual area-label assignment.
Changes:
- Makes prediction threshold configurable via repository variable
ISSUE_LABELER_PREDICTION_THRESHOLD - Changes default threshold from 0.40 to 0.05
- Updates three labeler workflow files consistently
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.github/workflows/labeler-train.yml |
Updated THRESHOLD to use configurable vars.ISSUE_LABELER_PREDICTION_THRESHOLD with 0.05 default |
.github/workflows/labeler-predict-pulls.yml |
Updated THRESHOLD to use configurable vars.ISSUE_LABELER_PREDICTION_THRESHOLD with 0.05 default |
.github/workflows/labeler-predict-issues.yml |
Updated THRESHOLD to use configurable vars.ISSUE_LABELER_PREDICTION_THRESHOLD with 0.05 default |
…beler.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
MihaZupan
approved these changes
Feb 16, 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.
We ran several training runs of the issue-labeler to evaluate different prediction thresholds. With input from several team members and a vote, we are lowering the threshold down to 0.05 to minimize the needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
occurrences.
This PR adds support for configuring the threshold via an
ISSUE_LABELER_PREDICTION_THRESHOLDactions env var, applying the 0.05 value as the default for this repo.