See #2749:
It would strictly link to the聽bug聽label, which is the most common label name.
We can't cover all cases (bugs, type: bug, etc.)
To generalize this, I guess it is better to search in the label and add it to Bugs if "bug" is found.
Interesting idea, but that may cause false positives 馃 (some repo may have tags like not-a-bug)
You should either take the individual approach like you are doing now and improve it by adding more to the list, or take the regex approach.
Interesting idea, but that may cause false positives 馃 (some repo may have tags like not-a-bug)
I would be surprised if such a label exists. This is so rare that we can add that to the ignore list. The chance of having not-a-bug is much less than the chance of people using other bug labels
The decision is up to you.
https://github.com/sindresorhus/refined-github/issues/2897
Another point to take into account is currently logical operators do not work (label:bug OR label::bug: Bug). So any other labels would require a brand new query for every repo.
I also _don't think_ its possible to do label like bug
2897
That's the issue I was looking for 馃槃
We鈥檙e limited by the search (and its API): it doesn鈥檛 accept regexes, so we can鈥檛 use them
@fregante Could you keep the issue open? This isn't solved yet. Having it open keeps this on the radar.
There's no radar if there's no way to solve it
Most helpful comment
https://github.com/sindresorhus/refined-github/issues/2897
Another point to take into account is currently logical operators do not work (
label:bug OR label::bug: Bug). So any other labels would require a brand new query for every repo.I also _don't think_ its possible to do
label like bug