GitHub Copilot integration: testers and contributors wanted (tracking issue)

Open
#132 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github, go, node.js, python, typescript, vscode

Research direction

Read docs/agent-installation.md#github-copilot and then packages/diffci-cli/src/client/agent-setup.ts to see exactly what diffci init writes, and agent-stop.ts for the stop-hook behaviour. Pick one checklist item and run its scenario against a real repository, capturing the observed payload or vendor documentation. Done means a PR or report with verified behaviour, or a clear note that the vendor documents nothing. The broad tracking scope and design questions make this unsuitable as a first contribution.

Written by the indexing model from the issue text.

Description

enhancement help wanted integration

DiffCI tells coding agents which tests and checks their change affects, so they verify before pushing. Since CLI 0.3.44, diffci init sets up GitHub Copilot: the diffci-verify skill (Copilot reads .claude/skills), the MCP server in the root .mcp.json for VS Code, and an agentStop hook in .github/hooks/diffci.json that sends the agent back when its change breaks tests. Setup: docs/agent-installation.md#github-copilot. None of this has been tried in a real Copilot session yet, and this area is open for contributors.

Steps (each is one PR or one report; take any):

  • #135 Copilot CLI: run diffci init, break a test, and confirm the agentStop hook blocks with the failure as the next prompt. Post the stdin payload you saw.
  • Copilot cloud agent: add the MCP JSON from the docs in repository settings and confirm the agent calls diffci_run_affected_tests before opening a PR.
  • VS Code agent mode: find out whether VS Code runs .github/hooks/*.json (GitHub's docs don't say), and whether the root .mcp.json loads without the experimental setting.
  • copilot-setup-steps.yml examples for common stacks (Node, Python, Go) so DiffCI can run the repository's tests in the cloud agent.
  • Use stop_hook_active from Copilot's payload alongside DiffCI's own attempt limit, if it helps.

Ground rules

  • When DiffCI cannot verify, the agent is told so and is never held: a failed setup must not look like a pass, and a pass must not be invented.
  • Verified behaviour only: link the vendor doc or show the payload you observed. If a vendor documents nothing, say so here rather than guessing.
  • Code lives in packages/diffci-cli/src/client/agent-setup.ts (what diffci init writes) and agent-stop.ts (the stop hook). Discuss design questions here, so every step stays consistent.

Area maintainer. Sustained work on this integration is how the Area maintainer tier is offered: named in the README and the docs, asked to review PRs that touch it, and co-author of the write-up when it ships.

Use Copilot and want to help, or have a repository we could test against? Say so below.

Dominant language
TypeScript
Stars
0
Forks
4
Avg merge
18h 41m
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DiffCI/core

All issues in DiffCI/core

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.