Infinite recursion in Bug issue submission help if VS Code on the Web?

[studyingegret]

• New Issue – Bug issue template:
  → https://github.com/microsoft/vscode-python/wiki/Reporting-a-bug
• https://github.com/microsoft/vscode-python/wiki/Reporting-a-bug if VS Code on the Web:
  → New Issue – Bug issue template

[Matheus Machado (Matheus-Machado750)]

[studyingegret]

Is this reply generated by an AI? The infinite recursion doesn't seem to be fixed, the navigation routes for VS Code on the Web have not changed. Neither the .github folder (except the actions) nor the wiki Reporting-a-bug page have been changed.

[studyingegret]

Please don't post comments like this if you don't really know how to solve it. I would've preferred it if you didn't say anything. If you reply to me like this any more, I'll block you. (And you don't seem to be a vscode-python maintainer.)

[ADARSH ANAND (iamAdarshAnand)]

This appears to be a documentation navigation loop rather than a problem with the Python extension itself.

The bug issue template links to the "Reporting-a-bug" wiki page for VS Code on the Web, but that page directs users back to the bug issue template.

A useful fix would be to make the web-specific instructions self-contained:

1. Explain which Python extension features are supported in VS Code for the Web.
2. Provide a direct link to the appropriate issue form.
3. Specify what information users should collect when desktop extension logs are unavailable.
4. Avoid linking users back to the same issue template without additional instructions.

For now, I suggest including the browser, operating system, reproduction steps, expected behavior, actual behavior, and any browser-console errors when reporting the problem.

This would also be a good documentation-only contribution because it could be fixed without changing extension behavior.