Vscode: Bot Proposal: "Caused by Extension X"

[JacksonKearl]

Background

We often get issues that should be filed on the extension's tracker. Currently the Inbox Tracker must find or memorize the extensions repo's URL and link to that with an explanation of the situation, or let the /causedByExtension command handle it, which provides limited guidance:

Proposal

This could be implemented as simply as a set of new actions for the commands bot:

/python => Close & Comment "This issue is likely caused by the Python extension. Please file a report at https://github.com/Microsoft/vscode-python."

Similar for /c, /cpp, /c#, /ts, /js (same as ts), /go, /powershell, /liveshare, /docker, and more as we see fit.

[isidorn]

I like this and would use it.

[IllusionMH]

Also would be useful for community members with access to bot commands.

[bpasero]

I like the idea, but we have to be careful that we are not sending people to extension repositories to report it there if it is totally unrelated to that extension. I am not sure that checking for words in the issue is sufficient.

[JacksonKearl]

@bpasero this would be triggered by the inbox tracker. So it's saving the inbox tracker from digging up the right urls rather than saving them from doing anything at all.

[JacksonKearl]

Added some commands to the existing commands action to do this. It will direct users to the issue reporting template or CONTRUBUTING.md based on whats available.

[jrieken]

Can you enumerate the list of supported commands? I have have tried /python but without success

[JacksonKearl]

\extPython
\extC
\extC++
\extTS
\extJS
\extC#
\extGo
\extPowershell
\extLiveShare
\extDocker

slashes are tilt-independent

[IllusionMH]

Works as expected 😆

[JacksonKearl]

Side note: as with the prior bot, commands that close issues will not leave comments if the issue was already closed.

[jrieken]

Can we also add /extJava please

[JacksonKearl]

One issue with Java is that there's a bunch of different popular Java extensions:

It's not clear to me to which we should link.

We could say:
If you're debugging, go here
If you're using language features, go here,
etc.

But I'm also not sure what the categories of features these all provide are, or if they're even mutually exclusive.

[jrieken]

wow - soo many options. I think the red hat language service and debugger are the popular ones

[JacksonKearl]

Added extJava and extJavaDebug.