Select importers when go.mod / go.sum dependencies change

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by reading #76 and the existing lockfile narrowing for yarn.lock/package-lock.json (#66), since this issue mirrors it for Go. The work lives where the Go adapter produces changed-package evidence: diff base/head go.mod require versions and go.sum, then use go list -deps Module.Path data to map local packages to external modules. Implement all listed fallbacks, and add the fixture where a imports github.com/x/y and b does not; done when bumping y selects only a and a replace change still falls back.

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

描述

adapter enhancement help wanted

Part of #76.

Any change to go.mod or go.sum falls back today (Language/framework configuration changed: go.mod). So does every Dependabot or Renovate bump. The JS side already narrows a lockfile change to the dependencies that changed (see yarn.lock/package-lock.json handling and #66), and Go can do the same.

Proposal

  • Diff the base and head go.mod (require versions only) and go.sum. When only the versions of some modules changed, select the local packages whose go list -deps closure includes a package from those modules.
  • The go list output already lists each dependency package's Module.Path, so the adapter needs to record, for each local package, which external modules it reaches.

Must fall back (blocker)

  • Any change to the go / toolchain line, replace, exclude, retract or godebug.
  • A changed module that go list can't resolve offline.
  • go.sum changes not explained by the go.mod diff.

Done when

  • A fixture where a imports github.com/x/y and b doesn't shows that bumping y selects only a, and adding a replace still falls back.
主要语言
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 摘要。