Onboard the GitHub Action based Issue-Labeler

[jeffhandley]

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:

• Home · dotnet/issue-labeler Wiki
• Onboarding · dotnet/issue-labeler Wiki

Once this is merged, I'll run the 'Labeler: Training' workflow to train new prediction models, then 'Labeler: Promotion' workflow to promote the models into active use, and then decommission the integration of the issue-labeler app for this repo.

[wtgodbe]

Thanks!

[jeffhandley]

Thanks, @wtgodbe. Based on feedback on another repo, I just augmented the workflows with more comments and a markdown doc. This should be good to merge though.

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. I probably don't have permission to do that, but I'm happy to answer questions or help with it.

Once those workflows are run, I will decommission this repo from the legacy service.

[jeffhandley]

/ba-g The failure is unrelated to adding these workflows

[jeffhandley]

@wtgodbe @danmoseley I was able to run the Training and Promotion workflows, the Cache Retention workflow, and then I ran an issue prediction and a pull request prediction run over the issues/pulls that had needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically . Everything validated, so I decommissioned this repository from the legacy labeler.