Skip to content

feat(go): manage Go dev tools via mise#203

Open
oyoshot wants to merge 2 commits into
mainfrom
go/expand-cli-tools
Open

feat(go): manage Go dev tools via mise#203
oyoshot wants to merge 2 commits into
mainfrom
go/expand-cli-tools

Conversation

@oyoshot

@oyoshot oyoshot commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add Go CLI tooling (golangci-lint, dlv, gofumpt, staticcheck, govulncheck, mockgen, gotests, impl, gomodifytags, golines) to mise so the same versioned binaries are available from both shell/CI and Neovim.
  • Use aqua:golangci/golangci-lint since upstream deprecates go install (some linters need pre-compiled binaries).
  • Drop go.nvim's update_all_sync build hook to prevent duplicate $GOPATH/bin installs that would shadow mise-managed versions.

Test plan

  • mise install succeeds for all new entries
  • Each new tool resolves via mise which / which to a mise shim or install path
  • golangci-lint version reports the aqua-distributed binary (not a go install build)
  • Open a Go file in Neovim and confirm gopls/format-on-save still works after dropping the build hook

🤖 Generated with Claude Code

oyoshot and others added 2 commits June 15, 2026 12:06
Centralize Go tooling (golangci-lint, dlv, gofumpt, staticcheck,
govulncheck, mockgen, gotests, impl, gomodifytags, golines) under mise
so the same versioned binaries are used from both the shell/CI and
Neovim. Drop go.nvim's update_all_sync build hook to avoid duplicate
$GOPATH/bin installs that shadow mise-managed versions. Use aqua for
golangci-lint since upstream deprecates `go install`.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant