4 ms·

> GitHub Issues, the product/feature, is clearly defined and encompasses things that deserve discussion, debate, or dispute. Except that GitHub Issues original

> GitHub Issues, the product/feature, is clearly defined and encompasses things that deserve discussion, debate, or dispute. Except that GitHub Issues originally only encompassed bugs. Labels weren't added until later that allowed you to filter by "type". Also, GitHub Discussions are for discussions, not GitHub Issues. GitHub themselves say that Issues is "often referred to as GitHub's bug-tracking system", so I wouldn't say that it's so "clearly defined". https://docs.github.com/en/get-started/quickstart/communicating-on-github https://docs.github.com/en/get-started/quickstart/communicat...

shkkmo 4y ago
> Also, GitHub Discussions are for discussions, not GitHub Issues. GitHub themselves say that Issues is "often referred to as GitHub's bug-tracking system" That quote is directly below a quite clear explanation of what issues are for: "are useful for discussing specific details of a project such as bug reports, planned improvements and feedback." Each project can decide for themselves at where they draw the line in terms of what they want where. That is a good thing, it makes github issues flexible for a wide range of projects that are organized in a wide variety of manners. It seems like a shame to lose that flexibility to make it easier for people who are too lazy to do more than look at the count of open issues when evaluating the health of a project.