3 ms·
And then you see it get marked as stale and closed after a month of inactivity. I hate that practice with a passion. I don't care there are 1000 issues open. I
by raro11 4y ago
And then you see it get marked as stale and closed after a month of inactivity.
I hate that practice with a passion. I don't care there are 1000 issues open. I do care there are 1000 unresolved issues closed by a bot.
I should create a bot that auto-replies "I believe this is still unresolved" for issues I have under the "File it" category!
- sph 4y ago"Beep boop! This issue hasn't had activity in 7 days. It will automatically close in 24 hours." I wish this bot had a physical manifestation so I could hit it with a wrench. "Issue closed as resolved by stupid-bot." And another +1 to the end-of-year KPI slides.
- mariusor 4y agoI think that's because maintainers consider tickets as action items for them personally instead of treating them as feedback documenting known issues(sometimes with workarounds) for their users. I think DeVault put it very well a while back: a ticket is the place where the community can gather and exchange feedback on a perceived issue with a project (I'm paraphrasing).