4 ms·
This is ridiculous. Not every issue means someone likes or even uses the codebase. Automated scanners, fuzzers, security researchers, and people who found an i
by junon 3y ago
This is ridiculous. Not every issue means someone likes or even uses the codebase.
Automated scanners, fuzzers, security researchers, and people who found an issue via a dependent codebase, are all examples where an issue might be filed but the person otherwise has no interest.
What a nonsense thing to have. It's not harmless, especially for large projects. It'll discourage and even runs the risk of artificially covering up potential security issues.
- ZoomZoomZoom 3y agoDon't forget, nobody prevents the user from opening an issue. If it's critical and the maintainers care, they'll work on it with or without the user's star.
- junon 3y agoI think you missed the part where the issue was closed by the bot for the user not having starred the repo, in which case - especially on high-traffic repos - the likelihood of actually seeing it is reduced.
- ZoomZoomZoom 3y agoMaintainers not auditing issues closed by their bots are irresponsible, but this problem is not related to the nature of the close-triggering condition.
- zokier 3y agoYou are assuming such drive-by issues are actually valuable; to me it is not 100% self-evident, especially when most projects do not have shortage of issues anyways.
- arp242 3y agoSome are, some are not. Assuming all are valuable would indeed be incorrect, but so would assuming all are worthless. In this case it's a "hey I want to make a patch, would you accept it?" type of question, and not really a bug report or feature request as such. I'd say that's valuable.