Regression on Github labels
#11
There are many branches of Minecraft, and there are many labels accordingly. I don't see a problem with that. It helps make lookups faster.

The current amount of labels is more or less static, it shouldn't grow further.

I wouldn't want to remove barely populated labels. Being small doesn't make them undesired. e.g. looking up all achievement problems is still a valid lookup use case, even if there aren't many such problems currently.

Furthermore, some labels have few issues because, in part, we have a backlog of unlabeled issues.

I don't know, I like it, and it's usefulTongue It's not like we're paying Github for each label. I did not zoom in to a boring resolution and do not intend to. I just had a label made for every major gameplay element and this is working nicely. At least, for me.
Reply
Thanks given by:


Messages In This Thread
Regression on Github labels - by sphinxc0re - 05-16-2016, 08:41 AM
RE: Regression on Github labels - by bearbin - 05-16-2016, 05:33 PM
RE: Regression on Github labels - by xoft - 05-17-2016, 04:40 AM
RE: Regression on Github labels - by sphinxc0re - 05-17-2016, 04:51 AM
RE: Regression on Github labels - by xoft - 05-17-2016, 04:55 AM
RE: Regression on Github labels - by LogicParrot - 05-18-2016, 08:30 PM
RE: Regression on Github labels - by LogicParrot - 05-18-2016, 08:39 PM
RE: Regression on Github labels - by LogicParrot - 05-18-2016, 08:48 PM
RE: Regression on Github labels - by LogicParrot - 05-18-2016, 10:10 PM
RE: Regression on Github labels - by bearbin - 05-19-2016, 05:24 PM
RE: Regression on Github labels - by LogicParrot - 05-19-2016, 08:41 PM
RE: Regression on Github labels - by tigerw - 05-25-2016, 02:08 AM



Users browsing this thread: 1 Guest(s)