Add virtual environment requirement to copilot instructions

[Copilot]

Copilot instructions now specify that all Python commands must be run in a virtual environment to prevent dependency conflicts and align with Python best practices.

Changes

• Added RULE 4: USE VIRTUAL ENVIRONMENTS to core principles

  • Mandates venv usage for all Python operations (pip, tox, pytest, etc.)
  • Provides platform-specific activation commands
  • Links to Python venv docs and Azure SDK dev setup guide

• Updated PYLINT and MYPY sections to require activated virtual environment as prerequisite

Example

# Create and activate virtual environment before running commands
python -m venv env
env\Scripts\Activate.ps1  # Windows PowerShell
source env/bin/activate   # Linux/Mac

# Then run Python commands
tox -e pylint --c <path_to_tox.ini> --root .

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• scanning-api.github.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

in the copilot instructions we should specify that all python commands should be run in a venv

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.