Try DiffCI on your repository: design partners wanted

Abierto
#86 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
15/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, go, java, python, typescript
Área
ci-cd, testing

Línea de trabajo

This is an outreach call for design partners, not a code task. Read docs/release-boundary.md for the supported stacks and examples/github-actions-check-plan.yml for the scheduled comparison setup. Optionally run the local npx @diffci.com/diffci check command on a real change. Done means commenting with your repository or stack, or emailing the maintainer, and saying whether a public repository may be replayed.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement help wanted

DiffCI works out what a change needs from CI, so you and your AI coding agents can run the right things before pushing. Required CI is never skipped. Today that means the tests and checks a change affects; build and deploy decisions (rebuild the image or not, deploy or promote) come next, and design partners shape them. We'd like a few more teams to try it on real repositories and tell us where it gets things wrong.

Supported today (details in the release boundary)

  • JavaScript/TypeScript: Vitest, pnpm workspaces, Vue components
  • Go: a root module
  • Java: conventional Maven reactors
  • Python: pytest (see #75)

When DiffCI isn't sure about a change, it runs the full suite and says why.

Try it locally (about 5 minutes, sends nothing anywhere):

npx --yes @diffci.com/[email protected] check --base origin/main --head HEAD

To compare it with your full suite over time, use the scheduled check-plan example. It reports any failure the selection would have missed. There's also the observer GitHub Action, which comments on PRs without changing what runs.

What you get

  • direct help setting it up
  • fixes for the cases that matter to your repository, first

What we ask

  • run it on real changes and share the reports, or only the fallback reasons if your code is private
  • tell us whenever it selected too little, or fell back to the full suite when it shouldn't have

Comment below with your repository (or just its stack) or email [email protected]. If your repository is public, say whether we may replay it. We'll only replay repositories whose maintainers say yes.

Lenguaje dominante
TypeScript
Estrellas
0
Forks
4
Merge medio
18 h 41 min
PR fusionados (30 d)
48

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DiffCI/core

Todos los issues de DiffCI/core

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.