Feature request: Scoped Labels #16682
Replies: 11 comments 9 replies
-
|
I came to ask this feature too, but scoped labels are not just a visual enhancement. They work as group labels, so if you have It miss a bit of configuration on GitLab, like:
Currently this feature on GitLab is incredibkly valuable and helpful, this is one of the reasons my company is on it. |
Beta Was this translation helpful? Give feedback.
-
|
Coming from GitLab over to GitHub this is definitely something I miss. My hunch is that GitHub would probably prefer to support this via a workflow or custom github action rather than as a native feature. |
Beta Was this translation helpful? Give feedback.
-
|
This is something Github lacks of... |
Beta Was this translation helpful? Give feedback.
-
|
This is the primary reason I still actively use GitLab for managing many orgs/projects. Custom action/workflow might work but they should provide an explanation of how to implement it |
Beta Was this translation helpful? Give feedback.
-
|
I would really love to see this added to GitHub, even if its a visual-only thing. It's one of the few features from GitLab I still miss when organising a project. I get that we can emulate the stateful labels using workflows, but there is no built-in protection against manually adding two labels with the same scope and things can get out of sync. |
Beta Was this translation helpful? Give feedback.
-
|
Just nudging this discussion again, as there's barely a day goes by without me wishing for this feature. |
Beta Was this translation helpful? Give feedback.
-
|
how do you manage this now? I am going from GitLab to GitHub and I am curious to see if anyone has dealt with it in any way that was helpful/manageable. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, I don't think there's any way to emulate this feature at the moment. |
Beta Was this translation helpful? Give feedback.
-
|
There's no reason why you can't create a workflow that does this for you. In go-task/task, we have some automation that uses github-script for our experiments workflow that is based off "scoped" labels. We name all our labels in the format: Currently, we're just using it to add comments to issues, but there is no reason why it couldn't be extended to also remove any other labels with the same scope. It's not perfect, but I think it's as close as you can get right now. |
Beta Was this translation helpful? Give feedback.
-
|
Bumping this thread in 2024. This is perhaps the only missing feature compared to gitlab... |
Beta Was this translation helpful? Give feedback.
-
|
With the work being done now in #139935, #139932, #139933, now seems like a more logical time than ever to have another look at this. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, it doesn't look like GitHub will ever implement this feature. |
Beta Was this translation helpful? Give feedback.
-
|
So it seems, but it would be awesome to get any kind of official response (even if it's a confirmation that it's nowhere on the roadmap) for that. |
Beta Was this translation helpful? Give feedback.
-
|
OMG yes, I've been wishing for this for years. I have SO MANY |
Beta Was this translation helpful? Give feedback.
-
|
This request or suggestions has been open for so long and never been answered or even in any way responded to by GitHub that I really believe that there is no real chance that it will ever happen. Sadly. 🥲 |
Beta Was this translation helpful? Give feedback.
-
|
In case it matters, Gitea has also had this feature for quite awhile now (https://docs.gitea.com/usage/labels#scoped-labels). |
Beta Was this translation helpful? Give feedback.
-
|
I would love to see this feature in GitHub. It really is one of the biggest things missing for versioning etc. for me. I really would love to have this feature here. I loved it when I used in GitLab for a project back then. |
Beta Was this translation helpful? Give feedback.
-
|
It was so useful when I used it in GitLab that I just assumed GitHub must've had the feature already (and I'd missed it somehow) |
Beta Was this translation helpful? Give feedback.
-
|
I'll add this: GitHub covers many of the use cases for scoped labels with fields on issues and product items. The issue HOWEVER, that's just excellent functionality with a limited reach. Those fields only cover a handful of use cases (clearly the most popular and important ones). They solve the core problem for those use cases: Categorization of issues that is configurable, easy to use, visually clear, and quick to interact with. Scoped labels extend the solution by allowing teams to choose the dimensions along which their issues will be categorized, and they do so without impacting the dimensions used by other organizations or teams. This allows a team to find and focus on the differentiations between issues that matter most to their org, team or development process. If they look for issues according to functional expertise, they may create a I'm pretty sure I'm not the only one looking into a way to implement scoped labels within GitHub without direct support from GitHub. I imagine the number of interested users would be easy to find by just looking up how many labels have a |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This pretty much regards labels of pull requests and issues.
GitLab uses a feature where users can use "scoped labels" which splits the labels apart. Where users create a label and just put in
::in between the parts that they want to split.So, for example, it could be used to create different categories of issues with
issue::translation, prioritiespriority::highor versioningrelease::V1.0.0. I believe it could have many more use cases and could generally help improve on managing/sorting pull requests or issues.Visual example (from Gitlab):
Beta Was this translation helpful? Give feedback.
All reactions