Turborepo adapter: read the task graph and run through `turbo run` (tracking issue)
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
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
Same shape as the Nx adapter (#111), after it works on one public repository.
- Read packages and task dependencies from
turbo.jsonand the workspace (turbo run test --dry=jsongives the resolved tasks,inputsand hashes). - A changed file that a task's
inputsmatch 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 liststurbo.jsononly 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
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DiffCI/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at randomPossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Agent tools: changed_files lists only the new path of a renamed filePossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
adapter good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·