Add Workflow to Tag Issues Missing Area Labels #78197
Open
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
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
JoeRobich
reviewed
Apr 22, 2025
|
@JoeRobich I have updated the logic and removed the 'Interactive-*' labels from consideration. However, there are still about 100 issues that will be affected. |
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 PR introduces a scheduled and manually-triggerable GitHub Actions workflow to identify and tag open issues that are missing an Area-* label in the dotnet/roslyn repository.
✅ Key Features:
Runs daily at 13:00 UTC and can be manually triggered.
Filters open issues that:
Do not have any Area-* label
Do not already have the
needs-area-labeltagAdds the label
needs-area-labelto such issuesSkips pull requests
Skips workflows running on forks (restricted to dotnet/roslyn)