Try DiffCI on your repository: design partners wanted

Ouverte
#86 0 commentaires 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é
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
15/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github-actions, go, java, python, typescript
Domaine
ci-cd, testing

Piste de recherche

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.

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

Description

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.

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.