-
Notifications
You must be signed in to change notification settings - Fork 767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a command that fills out the issue template #762
Comments
Here is something similar C# does using the clipboard to help users report issues. dotnet/vscode-csharp#2845 There seems to be a VSCode limitation on reading the output window though. |
Much better would be to encode the text into the new issue URL; this is what Go does for the |
Whatever, just save me from hunting down half a dozen of different pieces of info by clicking around in the UI and copying them to GitHub one at a time. :-) |
Of course, just throwing that there before I forget. 🙂 |
Huh, I just found a "Report issue" menu item under Help in VS Code Insiders. That solves my problem. Sorry! |
That may help for most, but I'm actually going to leave this open at the moment (if you don't mind) as we're working on a version which will auto-populate our template here with all of our required info as well as switch things over to the right logs, etc. |
This issue has been fixed in version 2021.1.1, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202111-13-january-2021 |
When I open a new bug I am asked for a bunch of version info that requires going back and forth copying and pasting versions of OS, vscode, extensions, pylance, etc. Why not add a little command to vscode that collects all these versions and prints them in the Markdown form the issue tracker requires? And then advertise that in the new issue template.
The text was updated successfully, but these errors were encountered: