GitHub Copilot integration: testers and contributors wanted (tracking issue)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 30/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github, go, node.js, python, typescript, vscode
- Área
- developer-experience, tooling
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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 theagentStophook 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_testsbefore 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.jsonloads without the experimental setting. -
copilot-setup-steps.ymlexamples for common stacks (Node, Python, Go) so DiffCI can run the repository's tests in the cloud agent. - Use
stop_hook_activefrom 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(whatdiffci initwrites) andagent-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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 0
- Forks
- 4
- Merge medio
- 18 h 41 min
- PR fusionados (30 d)
- 48
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DiffCI/core
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at randomPosiblemente ocupada @FredApps la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
Agent tools: changed_files lists only the new path of a renamed filePosiblemente ocupada @FredApps la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
DiffCI/core#243 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
adapter good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
Todos los issues de DiffCI/core
Issues similares
-
agent-ready area: ui-server priority: p3 type: test
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
schlessera/brain-kit#4249 ·
Los mantenedores suelen responder en 1 día
-
documentation tool triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
can1357/oh-my-pi#19608 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
dependencies tech-debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
bcgov/nr-waste-plus#1549 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
blixvip/solana-tx-parse#18 ·