I feel this has a lot less value in a world where you enable GitHub discussions. While not a panacea, it does remove the clutter of 'issues as discussions' and

I feel this has a lot less value in a world where you enable GitHub discussions. While not a panacea, it does remove the clutter of 'issues as discussions' and allows you to really use the issue tracker for just issues. This is what I would recommend every open source project do on GitHub: - Convert discussion issues to discussions - Label the existing issues as issue type (e.g. bug) if this makes sense for your project - Add an issue template that specifies if it is a feature request / discussion etc that it will be moved to discussions and they should proceed there, otherwise it can be filed as an issue - And importantly, close issues you don't intend to address, and a short explainer why (even if its just 'no longer relevant' or 'is not going to be considered, if requested open a new *discussion etc, make some boilerplate) That makes sense to me at least. I know discussions isn't perfect (far from it) however it cuts down the clutter on the issue tracker and makes it much easier I think to engage with the community (issues have this 'binding' status a lot of the times that discussions implicitly don't, so its much safer to spitball IMHO)