Turborepo adapter: read the task graph and run through `turbo run` (tracking issue)

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
ci-cd, testing

Research direction

Start with the existing Nx adapter referenced by issue #111 and inspect src/ci-inference/resolve.ts, where Turbo is currently treated as an opaque wrapper. Run turbo run test --dry=json in a public Turborepo monorepo to inspect resolved tasks, inputs and hashes, then compare how changed files select package tasks. The tracking issue is ready to evaluate once a public repository is available; done means Core can plan turbo run test --filter=<pkg>... and leave cache decisions to Turborepo.

Written by the indexing model from the issue text.

Description

adapter enhancement help wanted

Same shape as the Nx adapter (#111), after it works on one public repository.

  • Read packages and task dependencies from turbo.json and the workspace (turbo run test --dry=json gives the resolved tasks, inputs and hashes).
  • A changed file that a task's inputs match selects that package's task.
  • Plan turbo run test --filter=<pkg>... so Turborepo's cache decides what runs. File-level runs only in the agent's pre-push loop.
  • Today Core treats turbo as an opaque wrapper (src/ci-inference/resolve.ts) and lists turbo.json only as an implicit config file.

Looking for a public Turborepo monorepo to try it on. Comment if you maintain one.

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.