Skip to content
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

Automatically label GitHub issues #16106

Open
Piedone opened this issue May 20, 2024 · 7 comments
Open

Automatically label GitHub issues #16106

Piedone opened this issue May 20, 2024 · 7 comments

Comments

@Piedone
Copy link
Member

Piedone commented May 20, 2024

Is your feature request related to a problem? Please describe.

Labels help find related issues, like ones for GraphQL. However, adding labels is a chore, can only be done by a core contributor, and it's infrequent that we actually remember doing it.

Describe the solution you'd like

Try an auto-label solution like https://github.com/github/issue-labeler or https://github.com/Renato66/auto-label.

Describe alternatives you've considered

You can also use text search to find issues, of course, but an issue containing e.g. the "GraphQL" text doesn't necessarily actually mean that the issue is for the GraphQL module. This is also a problem with auto-labeling: a human needs to check. But that's still easier (and more apparent to do) than adding labels.

@hishamco
Copy link
Member

I remember that ASP.NET Core team did that back on the day, it was very helpful

+1 for labeling the issues

@Piedone
Copy link
Member Author

Piedone commented May 20, 2024

Do you have some pointers to that? That repo doesn't have a workflow for this.

@hishamco
Copy link
Member

I remember I have an ML model for that, let me check the GitHub workflow

@hishamco
Copy link
Member

https://github.com/dotnet/issue-labeler

I will recheck once I have time if that's the repo

@Piedone
Copy link
Member Author

Piedone commented May 20, 2024

Ah, interesting! This looks a bit too much of a heavy hitter for us (having to run an app for it) and Microsoft-specific but generally something that we could use.

@hishamco
Copy link
Member

You remind me of the time when the ASP.NET Core time unified the repos, then I saw a quick demo for an ML.NET model which was interested at that time to me :)

Copy link
Contributor

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

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

No branches or pull requests

3 participants