Document installation via go install - #35
Merged
Merged
Conversation
Leads with `go install github.com/richhaase/c2/cmd/c2@latest`, matching how bigboard documents itself, with a pinned-version form alongside it. The checkout-and-make path moves below, since it is now the least common way in. This does not work yet. The module proxy resolves @latest to the highest semver tag, which is v0.4.0 — the last TypeScript release, at a commit with no go.mod: $ go install github.com/richhaase/c2/cmd/c2@latest go: downloading github.com/richhaase/c2 v0.4.0 go: github.com/richhaase/c2/cmd/c2@latest: ... v0.4.0: verifying module A version tag on the Go code fixes both forms at once. The README names v0.5.0 in the pinned example on that assumption; if the first Go tag is numbered differently, that line needs to follow it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Leads the install section with
go install, matching how bigboard documents itself:with a pinned-version form alongside, and the checkout-and-
make installpath moved below since it is now the least common way in.This is blocked on a version tag
The command does not work yet, and it is worth knowing why before merging. The module proxy resolves
@latestto the highest semver tag, which is stillv0.4.0— the final TypeScript release, at a commit with nogo.mod:Cutting any version tag on the Go code fixes both forms at once, and
release.ymlwill build and attach the macOS and Linux binaries the README now points at. I have not cut one — that publishes a public release, which is yours to trigger.The pinned example names
v0.5.0on the assumption that is the next tag. If the first Go release is numbered differently, that line needs to follow it.🤖 Generated with Claude Code