-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Provide a command to dump info to help report an issue/bug #1119
Comments
We should use the full power of GitHub-flavoured Markdown and HTML5 as well, e.g. see #1125 and it's collapsible sections thanks to https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details . |
We might want to keep an eye out on the following issue microsoft/vscode#45673 |
Collection of user env may not be appropriate since we need to observe data collection and retention policies. 'Report issue' command may be suppressed by corporate IT policies and we can't bypass that. |
This is to generate a Markdown file that people can copy and paste into GitHub, so there's no IT policy that we would be going against unless a web browser is against policy. 😉 |
@rchiodo /cc (found it) |
We're going to close this for now. We'll revisit with a new issue in the future if needed. |
Not sure why this got a "data science" label (because of the "-review-" label?), but we actually hope to get to this some day. |
I was informed these would get closed. I added ds flag as we need this feature and xteam to benefit core team. |
Look for additional suggestions here: #12109 (comment) |
Completed in #17568 |
@paulacamargo25 what are the verification steps? |
Hi @tanhakabir, sorry it was accidentally marked as verification needed, the issue has already been tested here. |
If you run
Help: Report Issue
you get a pop-up window filled with system details that get used to pre-populate an issue. It would be great if we could do something similar for the details we have in our issue template by popping open a new tab with Markdown-formatted details.The text was updated successfully, but these errors were encountered: