Closed steveoh closed 4 years ago
I think it would be useful for deciphering the status of an issue at a glance, similar to open sgid issues.
I think it would be useful for deciphering the status of an issue at a glance, similar to open sgid issues.
Can you think of some useful labels?
I would worry about creating more process and required clicks. This almost seems like a good use-case for projects. However, that's a whole other can of worms. I would say that the labels might be nice for the GitHub-geeks to keep things organized, but I wouldn't make it any required part of the process.
I agree with Scott, there's a lot of T's to dot and I's to cross already. I'd vote to run a few feature classes through the process and if it seems like things are falling through the cracks then reevaluate the process.
I think it would be useful for deciphering the status of an issue at a glance, similar to open sgid issues.
Can you think of some useful labels?
I accept being outvoted at this point. If we revisit labels I will help to suggest some.
Describe the problem you are having
I think labels could help give context to the state of an open issue.
For additions something like...
We could do something similar with removals.
I wonder if you think this would be too much ceremony or if it would be helpful.