4 ms·
That's entirely right. This is more of a problem with the current workflow of the current implementation of GitHub Issues, for large projects -- it's absolutel
by jashkenas 14y ago
That's entirely right.
This is more of a problem with the current workflow of the current implementation of GitHub Issues, for large projects -- it's absolutely something that can be solved.
- gregmolnar 14y agoMaybe a kinda "Flag for close" button on the github interface would help with this. Than the community would be able to flag issues and the core devs could de-prioritize the flagged ones or if there are flags from enough members they can just close it without reading it assuming that many member is probably right?