Progress on cleansing issue list.

[mezotaken]

Earlier i pulled this PR and yesterday i labeled every issue (mostly automatically) and finally was able to clean up Feature Requests. 100+ solved and duplicate requests cleaned. Pretty sure its not all of them but if you wanted to join in on development - now it's time. There's only 466 of them. and now you finally able to see them all.
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement

Next job - managing bug-reports and bugs, Filtering those already fixed, obsolete and stale ones. And then there's Installation issues, which probably all will get appropriate label and will be transfered to discussions in new planned category "Installation Troubleshooting" as it seems to take 1/3 of all issues and discussions. I thought about 3 pinned threads for Windows, Linux and Mac.
I will consider all suggestions to making issue list really reflect current state of things, as well as every help with setting up new discussion category.
Btw github search still doesn't work normally, anybody knows why?

[ClashSAN]

Btw github search still doesn't work normally, anybody knows why?

Due to repo temporarily made private^ @mezotaken I get around this issue by googling. apparently google caches everything

github search WILL NOT WORK when searching existing issues or discussions, unless the issue post or discussion has received any interaction. then that post will show up again. Your enhancement labels helped. But the older bug reports stay at that dormant state.

[mezotaken]

i worked around it with gh cli tool. I retrieved the full list of issues+labels as a text file and just searched it in vscode.

[mezotaken]

To hell with it, let is stack to several thousands. It's impossible to manage 7 issues per hour on a regular basis.

[ClashSAN]

maybe we need a lovely - BOT-O-MATIC1111 to mark old issues as stale.

[mezotaken]

I can do this with one 5-line script in 5 minutes, but that's no solution because some bugs from sept/oct are still valid. This should help a bit #7217