chore: add mise, pre-commit, and lint tooling - #6
Merged
Conversation
Introduce .tool-versions, pre-commit (go + commitizen + markdownlint + golangci-lint), markdownlint config, and just init/lint/pre-commit recipes. Fix release builds by making the tray CGO-only with a clear stub when CGO is disabled.
Fix golangci-lint (errcheck, staticcheck, unused, gofmt, gosec config), expand unit tests across client/API/manager/hypervisor/agent/CLI and peers, and add just coverage + coverage-comment workflow (75% gate, cmd/tray excluded).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.tool-versions(Go, golangci-lint, pre-commit).cz.toml) for conventional commit-msg checksinit,lint,markdownlint,pre-commit,build-tray,coveragejust coverage→coverage.xml(cobertura); CI uploads artifact;coverage-comment.ymlposts PR table (minimum 75%, cmd mains + tray CGO excluded)CGO_ENABLED=0release builds succeedHow to test
After merge
Re-cut a CLI release (v0.2.1) so GitHub Release assets exist (v0.2.0 tag exists but publish failed).