Skip to content

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

jeffhandley
Copy link
Member

@jeffhandley jeffhandley commented May 13, 2025

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.

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
@jeffhandley jeffhandley requested a review from RussKie May 13, 2025 19:34
@RussKie
Copy link
Member

RussKie commented May 13, 2025

2025-05-13 19:36:01 [INFO]   File:[/github/workspace/.github/workflows/labeler-train.yml]
2025-05-13 19:36:01 [ERROR]   Found errors in [actionlint] linter!
2025-05-13 19:36:01 [ERROR]   Error code: 1. Command output:
------
.github/workflows/labeler-train.yml:23:15: input type of workflow_dispatch event must be one of "string", "boolean", "choice", "environment" but got "number" [syntax-check]
   |
23 |         type: number
   |               ^~~~~~

@jeffhandley
Copy link
Member Author

23 | type: number

That is a bogus lint error from the actionlinter. number is a valid type for workflow dispatch inputs:
https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputsinput_idtype

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.

@jeffhandley
Copy link
Member Author

jeffhandley commented May 14, 2025

Bumping superlinter to v7 addressed those lint issues. But now there are others to address. Will continue Wednesday Thursday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants