v2.1.0

Big thanks to @swathipil for contributing 2 significant features! 🚀

Referencing v2.1.0

To reference dotnet/issue-labeler v2.1.0 actions, workflows should pin to the SHA associated with the release as follows:

• uses: dotnet/issue-labeler/download@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0
• uses: dotnet/issue-labeler/train@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0
• uses: dotnet/issue-labeler/test@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0
• uses: dotnet/issue-labeler/promote@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0
• uses: dotnet/issue-labeler/restore@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0
• uses: dotnet/issue-labeler/predict@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0

Add discussion labeling to issues labeler workflow (#107)

GitHub Discussions are now supported and can be enabled using a separate model and a standalone workflow.

1. Update labeler-train.yml in your repository to add discussion support
   • See labeler-train.yml (v2.1.0) for a reference implementation
   • Be sure to invoke the train action using a pinned SHA from the v2.1.0 release branch (uses: dotnet/issue-labeler/train@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0)
   • This updated reference implementation also adds improved repository variable usage to allow more workflow configuration without code changes
   • Additional error handling is also added for the cases when insufficient data exists in the repository to conduct training (10+ issues/discussions/pulls needed)
2. Update labeler-promote.yml in your repository to add discussion support
   • See labeler-promote.yml (v2.1.0) for a reference implementation
   • Be sure to invoke the promote action using a pinned SHA from the v2.1.0 release branch (uses: dotnet/issue-labeler/promote@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0)
3. Add a new labeler-predict-discussions.yml workflow to your repository
   • See labeler-predict-discussions.yml for a reference implementation
   • Invoke the predict action using a pinned SHA from the v2.1.0 release branch (uses: dotnet/issue-labeler/predict@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0)

Add multi-label prediction support via max_labels input (#108)

Label prediction now allows multiple matching labels to be applied to issues, pull requests, and discussions. While most repositories prefer only having a single label applied within a label prefix group, there have been some scenarios where multiple labels are more appropriate--especially with discussions being supported.

1. When invoking the predictor app from a workflow, set the max_labels input. The default is 1.

Set GH_REPO so gh cache delete can resolve the target repository in the promote action (#109)

This updates the promote action to fix an issue where an existing target cache entry could not be deleted. This compensates for a change in behavior on GitHub's action runner.

1. Update your labeler-promote.yml workflow to reference the promote action using a pinned SHA from the v2.1.0 release branch: uses: dotnet/issue-labeler/promote@98f1d9b85686147ffdc155547cdd3469546c4e26 # v2.1.0