Red-builds study: GitHub Copilot cloud agent PRs

Aperta
#136 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, github-actions, typescript

Direzione di ricerca

Read docs/red-builds.md and the Copilot integration work in #132, then inspect packages/diffci-cli/src/client/red-builds.ts and the diffci red-builds JSON output. Run the study using the read-only GitHub API and the specified CLI command, preserving denominators and separating Copilot PRs from all PRs. Done means a reviewed report with the requested per-repository table and notes on unrecognised job names.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

benchmark contribution help wanted integration

diffci red-builds (docs/red-builds.md) reads a repository's PR CI history and classifies each red build: could the change's own tests and checks have caught it before the push, or was it flaky, infrastructure, already broken on main, or CI-only? This study runs it on PRs opened by GitHub Copilot's cloud agent, to measure how many of an agent's red builds were preventable inside its own loop. It goes with the Copilot integration work in #132.

Method

  1. Find public repositories where Copilot's cloud agent opens PRs (head branches starting copilot/). Use the authenticated, read-only GitHub API only, one request at a time, at least 1.2 s apart, stopping below 1,000 remaining requests. Collect no personal data.
  2. Run diffci red-builds <owner/repo> --runs 200 --json (CLI 0.3.45 or later) on each repository, one at a time.
  3. Split the results into Copilot PRs (copilot/ branches, which AGENT_BRANCH in packages/diffci-cli/src/client/red-builds.ts already recognises) and all other PRs. If the JSON doesn't record each run's head branch, add that to the CLI first rather than inferring it.

Report

  • One row per repository: workflow, window, PR runs, red, preventable, partly, unconfirmed, shared (main already broken), CI-only, flaky, infra, and preventable runner-minutes. Show Copilot PRs and all PRs side by side.
  • Keep every denominator. Preventable counts are upper bounds: classification uses job types and failure annotations, not a DiffCI plan for each commit.
  • Note repositories where the job names weren't recognised and the run fell to CI-only.

Ground rules

  • Read-only. No comments, issues or PRs in the studied repositories as part of this study.
  • Results are published here only after a maintainer has reviewed the numbers.
  • No test replays: this reads CI history only.

Help wanted: if your own repository uses Copilot's cloud agent, you can run step 2 on it and post the table row below.

Lingua principale
TypeScript
Stelle
0
Fork
4
Merge medio
18h 41m
PR unite (30g)
48

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DiffCI/core

Tutte le issue di DiffCI/core

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.