Support build tags
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go
- 领域
- build-system, testing
调研方向
The fallback happens when GOFLAGS is non-empty or a .go file falls outside the active build context. Start by finding where GOFLAGS is checked and where the build-context fallback messages are produced, then trace how go list is invoked. The done condition is a fixture with foo_integration_test.go behind //go:build integration: with the tag declared in diffci.json, a change to foo.go selects the package under both tag sets, and without the declaration it still falls back. Because the design is still open, confirm the -mod=readonly question before coding.
由索引模型根据 Issue 内容生成。
描述
Part of #76.
Any non-empty GOFLAGS falls back:
Go custom build flags or incomplete build context require full validation
Files behind a tag that isn't active also fall back (Go files outside the active build context require full validation: …). Repositories with //go:build integration test files hit this constantly.
Proposal
- Accept
GOFLAGSwhen it contains only-tags=...(and maybe-mod=readonly). Pass the same flags togo listand put them inexecutionEnv, so thego testcommand uses the build context that was analysed. - Let
diffci.jsondeclare extra tag sets (for example"go": { "tags": [[], ["integration"]] }). Rungo listonce per set, merge the packages, and emit one command group per set.
Must fall back (blocker)
- Any other
GOFLAGSentry (-ldflags,-gcflags,-overlay, ...). - A
.gofile that none of the analysed tag sets or platforms includes.
Done when
- A fixture with
foo_integration_test.gobehind//go:build integrationshows that, with the tag declared, a change tofoo.goselects the package under both tag sets, and without the declaration it still falls back.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 4
- 平均合并
- 18 小时 41 分钟
- 30 天内合并 PR
- 48
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
DiffCI/core 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at random可能已有人在做 @FredApps 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复
-
Agent tools: changed_files lists only the new path of a renamed file可能已有人在做 @FredApps 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
adapter good first issue
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
相似的 Issue
-
agent-ready area: ui-server priority: p3 type: test
难度 2/5 1-3 小时 新手友好度 78/100
schlessera/brain-kit#4249 ·
维护者通常 1 天内回复
-
documentation tool triaged
难度 2/5 1-3 小时 新手友好度 73/100
can1357/oh-my-pi#19608 · 2 条评论 ·
维护者通常 1 天内回复
-
dependencies tech-debt
难度 2/5 1-3 小时 新手友好度 65/100
bcgov/nr-waste-plus#1549 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 78/100
blixvip/solana-tx-parse#18 ·