Onboard the GitHub Action based Issue-Labeler#78426
Merged
arunchndr merged 3 commits intodotnet:mainfrom May 8, 2025
Merged
Conversation
arunchndr
approved these changes
May 7, 2025
| fail-on-cache-miss: ${{ env.ALLOW_FAILURE }} | ||
| quiet: true | ||
|
|
||
| - name: "Predict issue labels" |
There was a problem hiding this comment.
fascinating!
does this use the previous training from the old labeler by any chance or do we start over?
Member
Author
There was a problem hiding this comment.
You have to re-train but now it's all self-service within each repository, and no services to run, storage to manage, or anything else outside GitHub Actions. But the logic for building the new model is the same as the old implementation (but muuuuuuuccch faster and easier). When you run the 'Labeler: Training' job, the job summary will show the new model's accuracy based on test results where it re-predicts existing issue/pulls in the repository and compares the new prediction against the existing labels.
This was referenced May 10, 2025
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
3 participants
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.
These workflows replace the issue-labeler implementation that runs as a GitHub app, allowing training and prediction for the repository's labels without the need for an external service.
References:
Once this is merged, we'll need to run the 'Labeler: Training' workflow to train new prediction models, then 'Labeler: Promotion' workflow to promote the models into active use, and then I can decommission the integration of the legacy issue-labeler app for this repo.
The legacy issue-labeler was also applying the untriagedIssues and PRs which have not yet been triaged by a lead
label to new issues and pull requests, but there's also a
resourceManagementpolicy in this repo for managing the untriaged label. With this migration to the GitHub Action based issue-labeler, the issue-labeler will no longer apply that label, so only the resource management policy will apply for that.