Support repositories with several go.mod modules

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, typescript
领域
ci-cd, testing

调研方向

Start with tracking issue #76 and the related go.work issue, then locate the Go module analysis and fixture tests. Check how go list results and module-to-file assignment are handled, and coordinate on the tracking issue as requested. Done when a fixture with a root module and tools/go.mod selects only tools tests for changes in tools/, without a go.scope setting.

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

描述

adapter enhancement help wanted

Part of #76.

A repository with a root go.mod plus nested modules (for example tools/go.mod or examples/go.mod) falls back unless it sets "go": { "scope": "root-module" }. Even then, changes inside the nested modules always fall back:

Changes in a Go module outside the declared root-module scope require full validation

Proposal

  • Analyse every module in the repository, not just the root: run go list from each go.mod directory and merge the results.
  • A nested module that requires another in-repo module by module path, with no local replace, uses the published version, so there's no edge. Only a local replace creates an edge (see the replace issue).
  • Keep go.scope: root-module as an opt-out for repositories that want the current behaviour.

Must fall back (blocker)

  • Any module whose go list fails, or whose files can't be assigned to exactly one module.

Done when

  • A fixture with a root module and tools/go.mod shows that a change in tools/ runs only tools tests, without any go.scope setting.

Shares most of its code with the go.work issue. Whoever picks up either one, coordinate on the tracking issue.

主要语言
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 摘要。