Nx adapter: read the Nx project graph and run through Nx (tracking issue)

未关闭
#111 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start with src/ci-inference/resolve.ts and src/planner/test-command.ts, then review the tracked work in issues #112–#114. The issue describes reading Nx's project graph, selecting targets, and planning nx run-many commands, but leaves the implementation and public workspace validation as multi-step design work. Done means checks are covered, selected projects are compared with nx affected, and Nx cache hits remain intact.

由索引模型根据 Issue 内容生成。

描述

adapter enhancement help wanted

DiffCI should work alongside Nx, not instead of it. In a repository with Nx installed, DiffCI reads Nx's project graph, adds the file-level and check edges Nx doesn't model, and hands execution back to Nx. Nx's task runner and cache still decide what actually runs.

Today. Core treats nx as an opaque wrapper (src/ci-inference/resolve.ts). A root test script that calls nx is assumed to run every package, and the plan refuses when a package can't be narrowed (src/planner/test-command.ts, runsWorkspaceScripts). nx.json is never read as data.

Plan

  • Map files and test files to Nx projects from nx graph (#112)
  • Select a project's target when a changed file matches its Nx inputs / namedInputs (#113)
  • Plan nx run-many commands for the selected projects (#114)
  • Docs: using DiffCI in an Nx workspace (extends #101)

Principles

  • Nx's edges only add reach. They never remove an edge DiffCI's own graph found.
  • The default command is project-level (nx run-many -t test -p a,b), so Nx's cache keys don't change. File-level runs (nx run a:test -- <files>) change the task hash and are only for the agent's pre-push loop.
  • If DiffCI's plan and Nx's cache disagree, the cache decides whether a task runs. DiffCI only narrows or explains.
  • When Nx can't produce a graph, DiffCI falls back to the full suite and says why.

Success. On a public Nx workspace with inferred targets: checks covered before the push, projects run compared with nx affected, and Nx cache hits left intact.

Out of scope: replacing Nx's cache, distributed execution or sharding.

主要语言
TypeScript
星标
0
派生
4
平均合并
18 小时 41 分钟
30 天内合并 PR
48

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DiffCI/core 的其他 Issue

查看 DiffCI/core 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。