chore: install the whole build, run and test toolchain through mise, and consider mise tasks in place of Taskfile
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 12/100
- Issue 类型
- 重构
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- build-system, ci-cd, tooling
调研方向
Start with mise.toml, the go.tool*.mod files, Taskfile.yml and .github/actions/install-task/action.yml to see how tools are installed today. Then read internal/upgrade/taskfile_shape_test.go, which pins the CI jobs to task targets, and scripts/vuln_report.py, which lists the tool roster. Done means the D-04 tool-sourcing decision and the task-runner decision are recorded, with the required job names still intact. This is design work, so check with the maintainer before writing any code.
由索引模型根据 Issue 内容生成。
描述
The build, run and test tools reach a machine in four different ways, and none of them pins the Go toolchain itself. Move the whole tool suite into mise, and consider mise tasks in place of Taskfile.yml.
What exists today (main at 8c0107f1)
-
Go tools are built from five isolated modfiles:
go.tool.mod: task, goreleaser, govulncheckgo.tool-changie.mod: changiego.tool-golangci.mod: golangci-lintgo.tool-lint.mod: actionlintgo.tool-proto.mod: buf, protoc-gen-go, protoc-gen-connect-go
CI builds
taskthrough.github/actions/install-task, and the Taskfile runs the rest throughgo tool -modfile=.... -
Go comes from
actions/setup-gowithgo-version-file: go.modin CI, and from whatever Go is on the machine locally. Ambient Go 1.27 cannot buildcockroachdb/swiss, so every localtask testneedsGOTOOLCHAIN=go1.26.10, and the Taskfile hard-codes that pin in several places (#104). -
Node and pnpm:
actions/setup-node(Node 24) andweb/package.json'spackageManager: [email protected]. -
mise already pins
hkand@fission-ai/openspecinmise.toml, withmise.lockfor linux-x64, linux-arm64 and macos-arm64. -
Python is the runner's
python3. #177 covers it. -
Tasks:
Taskfile.ymlholds about 6,200 lines and 73 top-level tasks. CI runstask <target>in every workflow (43 uses inci.yml).
What to do
- Pin every tool in
mise.toml: Go (from go.mod'sgoline, which also closes the local half of #104), task or its replacement, goreleaser, govulncheck, changie, golangci-lint, actionlint, buf and the protoc plugins, Node, pnpm, uv, hk and openspec. Keepmise.lockfor all three platforms. - Use one bootstrap for local and CI. Locally that is
mise install. In CI it is eitherjdx/mise-actionor a composite action that keeps D-04 (below). - Retire the
go.tool*.modfiles once mise owns those tools, and point the tool roster thattask vulnscans (scripts/vuln_report.py) at the mise-installed binaries. - Evaluate mise tasks (
[tasks]inmise.toml, or file tasks under.mise/tasks/) as a replacement forTaskfile.yml, as a separate step after the tools move.
Decisions needed
- D-04, how CI gets tools.
.github/actions/install-task/action.ymlsays every CI build tool is built from the checksummed Go module proxy and never from a GitHub Releases download or an install script, after CDN outages brokearduino/setup-taskandtaskfile.dev/install.shin holomush. mise'sgo:backend keeps that for the Go tools, because it runsgo installthrough the proxy. Theaqua:andubi:backends, andjdx/mise-actionitself, download release binaries. Decide per tool, and record the decision. - Taskfile vs mise tasks.
internal/upgrade/taskfile_shape_test.gomakes everyci.ymljob a registeredtask <target>run (inScopeJobs,runBodyExceptions). Moving to mise tasks means rewriting that guard. Several Taskfile targets also carry long, load-bearing comments: the golden suite, the tmux e2e, release rehearsal and fragment checks. - Required checks. The
protect-mainruleset pins its required checks by job name. The migration must keep every job name.
Suggested order
- Pin Go, Node, pnpm and uv in mise, and use them locally.
- Move the Go-built tools to mise
go:entries, and switch CI bootstrap with D-04 kept or explicitly revised. - Decide on the task runner.
Related: #104 (Go toolchain pin), #177 (uv), #176 (the mutation-check script).
🤖 Generated with Claude Code
- 主要语言
- Go
- 星标
- 0
- 派生
- 0
- 平均合并
- 7 小时 42 分钟
- 30 天内合并 PR
- 111
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
seanb4t/codegraph-go 的其他 Issue
-
chore needs-triage
难度 1/5 1 小时以内 新手友好度 88/100
seanb4t/codegraph-go#380 ·
维护者通常 1 天内回复
-
chore needs-triage
难度 2/5 1-3 小时 新手友好度 82/100
seanb4t/codegraph-go#379 ·
维护者通常 1 天内回复
-
area:query chore needs-triage spec-needed
难度 2/5 1-3 小时 新手友好度 74/100
seanb4t/codegraph-go#377 ·
维护者通常 1 天内回复
-
chore needs-triage
难度 1/5 1-3 小时 新手友好度 84/100
seanb4t/codegraph-go#362 ·
维护者通常 1 天内回复
-
area:query bug needs-triage
难度 2/5 1-3 小时 新手友好度 80/100
seanb4t/codegraph-go#355 ·
维护者通常 1 天内回复
查看 seanb4t/codegraph-go 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
automated documentation maintenance
难度 1/5 1-3 小时 新手友好度 75/100
github/gh-aw-mcpg#16717 ·
维护者通常 1 天内回复
-
Docs: Recording rules pages don't say what happens to a recorded metric when its rule is deleted未关闭internal
难度 1/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 74/100
jesseduffield/lazygit#6229 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
prometheus/prometheus#20482 ·
维护者通常 2 天内回复