Red-builds study: GitHub Copilot cloud agent PRs

Ouverte
#136 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github, github-actions, typescript

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
0
Forks
4
Merge moyen
18 h 41 min
PR mergées (30 j)
48

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de DiffCI/core

Toutes les issues de DiffCI/core

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.