Add GitHub issue templates (Bug Report, Feature Request, Question)

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,81 @@
+---
+name: Bug Report
+about: Create a report to help us improve.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+Please search existing issues first to avoid creating duplicates:
+https://github.com/microsoft/vscode-python-environments/issues
+-->
+
+## Environment data
+
+<!--
+To find extension versions, open the VS Code Extensions panel and locate each
+extension from the list of installed extensions. The version appears next to the name.
+-->
+
+-   Python Environments extension version: XXX
+-   Python extension (`ms-python.python`) version: XXX
+-   VS Code version (Help → About): XXX
+-   OS and version: XXX
+-   Python version (& distribution if applicable, e.g. Anaconda): XXX
+-   Environment manager in use (`venv` / `conda` / `pyenv` / `poetry` / `pipenv` / `system` / `uv` / other): XXX
+-   Shell (bash / zsh / fish / pwsh / cmd / other): XXX
+-   Remote / container scenario (none / WSL / SSH Remote / Dev Container / Codespaces): XXX
+-   Workspace type (single folder / multi-root / mono-repo): XXX
+-   Is this a regression? If yes, last known working extension version: XXX
+
+## Repro Steps
+
+<!--
+Please list the minimal steps needed to reproduce the issue, starting from a fresh
+VS Code window when possible. If the issue only reproduces with specific workspace
+contents (e.g. a `pyproject.toml`, `.venv`, `environment.yml`, `Pipfile`, `poetry.lock`,
+`.python-version`), please share a minimal example or describe the layout.
+
+If the bug only reproduces with certain settings, please include the relevant entries
+from your `settings.json` (user and/or workspace).
+-->
+
+1. XXX
+
+## Expected behavior
+
+XXX
+
+## Actual behavior
+
+XXX
+
+## Logs
+
+<!--
+Please include logs from the "Python Environments" output channel.
+
+To capture verbose logs:
+1. Open the Output panel (View → Output).
+2. Select "Python Environments" from the channel dropdown in the upper-right.
+3. Click the gear / filter icon at the top of the Output panel and set the level to "Trace".
+   (Alternatively: Command Palette → "Developer: Set Log Level…" → "Python Environments" → "Trace".)
+4. Reproduce the issue.
+5. Paste the relevant output below, or save it to a `.txt` file and attach it to the issue (preferred for long logs).
+
+If the issue is about terminal activation, please also paste the exact terminal
+output where the problem occurs.
+-->
+
+```
+XXX
+```
+
+## Additional context
+
+<!--
+Anything else that may help us reproduce: screenshots, videos, related issues,
+links to your project, workarounds you've tried, etc.
+-->

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,12 @@
+---
+name: Feature Request
+about: Suggest an idea for this project.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!-- Please search existing feature requests to avoid creating duplicates. -->
+
+<!-- Describe the feature you'd like. -->

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,19 @@
+---
+name: Question
+about: Ask a question about this project.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+Please search existing issues to avoid creating duplicates.
+For general Python-in-VS-Code usage questions, consider starting a discussion at
+https://github.com/microsoft/vscode-python/discussions/categories/q-a
+or checking the issues in the following related repositories:
+- Python extension: https://github.com/microsoft/vscode-python/issues
+- Pylance: https://github.com/microsoft/pylance-release/issues
+- Jupyter: https://github.com/microsoft/vscode-jupyter/issues
+- Python Debugger: https://github.com/microsoft/vscode-python-debugger/issues
+-->