Onboard the GitHub Action based dotnet/issue-labeler for area- label predictions #5121
Conversation
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
jeffhandley
requested review from
MichaelSimons,
premun and
mthalman
as code owners
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.
This repository has had the legacy dotnet/issue-labeler service enabled for a long time, but it doesn't seem to have been actively labeling issues with
area-label prefixes. We are working to decommission the legacy service that runs as a GitHub App backed by Azure services, and replace it with the new implementation that uses GitHub Actions instead.This PR adds the workflows required for onboarding to dotnet/issue-labeler (which is different from the github/issue-labeler). Once merged, the "Area Labeler: Training" and "Area Labeler: Promotion" workflows can be run to train an ML.NET model on the repository's issues and PRs for it to then be able to start predicting
area-labels as new issues and PRs are created.For further information, see:
These workflows can run alongside the existing labeler workflow that adds the https://github.com/dotnet/dotnet-docker/labels/untriaged label to new issues.