Packaging and Distributing a CLI Tool Written in Go
Writing a Go CLI is half the work; versioning it, cross-compiling it and distributing it so others can install it effortlessly is the other half.
Tag
Building applications and tools in Go: concurrency, error handling and the standard library.
There are 19 posts with this tag.
Writing a Go CLI is half the work; versioning it, cross-compiling it and distributing it so others can install it effortlessly is the other half.
Architecture decisions stay true on the wiki and rot in the code. archlint enforces the boundaries in architecture.json on every commit, no model.
In a polyglot repo the rule is the same in every language; one architecture.json now enforces Go, TypeScript and Python boundaries in CI.
I added a deterministic flaky-test filter to CommitBrief: it catches hard-coded sleeps and unseeded randomness at commit time, with no model.
Two new commands: summary briefs a change and its history, and remote pr reviews a PR from the terminal, leaving comments before the human does.
Not the 'why' but the 'how much': which workflow layers the tool plugs into, the bug patterns it keeps catching, and where it hits its limits.