search

OrchardCMS / OrchardCore

Orchard Core is an open-source modular and multi-tenant application framework built with ASP.NET Core, and a content management system (CMS) built on top of that framework.
https://orchardcore.net
BSD 3-Clause "New" or "Revised" License
7.44k stars 2.4k forks source link

Automatically label GitHub issues #16106

Open Piedone opened 6 months ago

Piedone commented 6 months ago

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 commented 6 months ago

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

+1 for labeling the issues

Piedone commented 6 months ago

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

hishamco commented 6 months ago

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

hishamco commented 6 months ago

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

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

Piedone commented 6 months ago

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 commented 6 months ago

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 :)

github-actions[bot] commented 5 months ago

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.