-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Onboard the dotnet/issue-labeler for 'area-' label prediction on issues #9889
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Configure the issue-labeler training workflow. - Imported the workflow template - Removed inputs, jobs, and conditions related to pull requests, as we will only use the labeler for issues in this repository
Configure the issue-labeler promotion workflow. - Imported the workflow template - Removed input and job for pull requests, as we will only use the labeler for issues in this repository
Configure the issue-labeler issue prediction workflow. - Imported the workflow template - Removed the excluded_authors input
Configure the issue-labeler cache retention workflow. - Imported the workflow template - Removed config related to pull requests, as we will only use the labeler for issues in this repository
|
That is a bogus lint error from the actionlinter. So far, I'm striking out figuring out how to configure superlinter to ignore that warning and/or ignore the workflows. The yaml lint errors are also... irritating, but presumably could be addressed. |
Bumping superlinter to v7 addressed those lint issues. But now there are others to address. Will continue |
The dotnet/issue-labeler uses an ML.NET model trained from this repository to automatically predict and apply labels to new issues. This onboards the labeler into the dotnet/core repository, configuring it to predict
area-
labels on new issues. Pull requests will not be labeled.