Conversation
Co-authored-by: ncrmro <8276365+ncrmro@users.noreply.github.com>
Co-authored-by: ncrmro <8276365+ncrmro@users.noreply.github.com>
|
I have read the CLA Document and I hereby sign the CLA 1 out of 2 committers have signed the DCO. |
|
@copilot fix 2026-01-22T23:50:50.5911967Z ##[group]Run echo "Python version:" |
Co-authored-by: ncrmro <8276365+ncrmro@users.noreply.github.com>
|
@copilot leave the original commented out nix code to explain the situation as nix would be the preferred environment |
Co-authored-by: ncrmro <8276365+ncrmro@users.noreply.github.com>
Added in 910c40e. The commented Nix setup now includes a note explaining that Nix is the preferred environment but causes Copilot agent Bash tool calls to silently hang, which is why we're using the uv/Python setup as a workaround. |
There was a problem hiding this comment.
@copilot create .github/copilot-instructions.md that indicates how development can be done given these setup steps.
It should only really document this leaving the primary context defined in AGENTS.md
There was a problem hiding this comment.
Created in ec99005. The .github/copilot-instructions.md file documents:
- Environment setup steps (uv, Python 3.11, dependencies)
- Available tools and how to use them via
uv run - Development workflow (testing, linting, type checking)
- Why Nix isn't used for Copilot workflows
- References to
AGENTS.mdfor primary context
… Copilot agents Co-authored-by: ncrmro <8276365+ncrmro@users.noreply.github.com>
There was a problem hiding this comment.
@copilot make this terse, it should only document the AGENTS.md and the tools available as well as instructions for running tests
There was a problem hiding this comment.
Made terse in fb2f320. The file now only includes:
- Reference to AGENTS.md for primary context
- Available tools table (pytest, ruff, mypy, deepwork)
- Test running instructions
Reduced from 128 lines to 35 lines.
…ols, and tests Co-authored-by: ncrmro <8276365+ncrmro@users.noreply.github.com>
Plan: Update copilot-setup-steps.yml to have working setup environment
uv runinstead ofpython -mfor tool verification.github/copilot-instructions.mddocumenting development setupSummary of Changes:
The
.github/workflows/copilot-setup-steps.ymlworkflow has been successfully updated from a non-functional skeleton (with all steps commented out) to a fully working workflow that sets up a complete Python development environment.What Changed:
release.ymlandclaude-code-test.ymluv runto execute pytest and ruff in the virtual environment (fixed CI failure).github/copilot-instructions.md- Concise documentation for Copilot agents (references AGENTS.md, lists tools, provides test commands)Workflow Steps:
actions/checkout@v4astral-sh/setup-uv@v4actions/setup-python@v5actions/cache@v4uv sync --extra devuv run)Usage:
The workflow can be used in three ways:
workflow_callworkflow_dispatchfrom GitHub UIDocumentation:
.github/copilot-instructions.md- Terse guide for Copilot agentsValidation:
✅ YAML syntax validated
✅ Code review passed with no issues
✅ CodeQL security scan passed with no vulnerabilities
✅ Pattern follows established working workflows in the repository
✅ CI failure fixed - tools now run in virtual environment via
uv run✅ Documented why Nix setup is not used (Copilot agent compatibility issue)
✅ Created concise Copilot development documentation
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.