twic
On the one hand, sure. On the other hand, the original issue he's complaining about is:
> Copilot in Agent mode diffs become hard to comprehend #260436
> Steps to Reproduce:
> 1. Try vibe coding like activity
> 2. See how the edits become hard to comprehend
And when a bot asked for more details, linking to a human-written document which explicitly mentions things like VSCode version, and "what you actually saw", he did not reply. It's a garbage bug report, and it's quite right that it was closed.
Zambyte
"he" is OP btw. Instead of adding the requested details, OP made another issue complaining about the bot closing their issue, and then posted their own issue to HN. This seems like a lot more effort than actually adding the requested information in the first place.
verdverm
(1) I've seen the bot close the issue anyway with the details populated from VS Code
(2) In many cases, those details are irrelevant to the issue. They know it is programmed that way for a while and it could be debated whether it is a bug or design limitation. (like closing the current terminal when starting a new chat)
Regardless, they are keen to use more bots rather than humans for handling triage and I personally think it's not a good idea because the bots are not up to the task. Too many rules and mistakes, separates those who appreciate feedback in any form from those who see it as uninteresting work
verdverm
I didn't see it before the bot assigned a human and then closed it anyway
If you appreciate feedback, you'll take it in any form. If they are so good at AI, then they should be able to do much better than this automated garbage
firesteelrain
We do the same thing at work with Jira. If a ticket doesn’t get moved to a state then it is auto closed and the reporter has to advocate for it to be reopened. I guess it’s a bot but really it’s just ScriptRunner.
If you don't want to put the basic amount of effort to follow the repository bug reporting guidelines, why should the developers put any effort into responding?