Try DiffCI on your repository: design partners wanted

Open
#86 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, go, java, python, typescript
Domain
ci-cd, testing

Research direction

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.

Written by the indexing model from the issue text.

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.

Dominant language
TypeScript
Stars
0
Forks
4
Avg merge
18h 41m
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DiffCI/core

All issues in DiffCI/core

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.