Repository navigation
Adopt Go-TOPS: a gate job beside check - #24
Merged
Merged
Conversation
Adds the Go-TOPS gate to vigil under enforce: ratchet. The check job, .golangci.yml, ci.yml, go.mod and go.sum are unchanged. - go-tops.yaml and go-tops.lock; tools/go.mod and tools/go.sum pin gotops at v0.0.0-20261119162302-608716388245, a pseudo-version of go-tops main (no tag, no replace). - .github/workflows/go-tops.yml: the gate job with ubuntu, macos and floor legs, its own name and concurrency group. - .go-tops/golangci.yml: the lint rules the gate reads; the repository's own .golangci.yml is not read by the gate and is not changed. - GO-TOPS.md, the AGENTS.md block, justfile, a CODEOWNERS fragment and .gitignore lines. No ledger is committed. The ubuntu leg writes the first one on this pull request and uploads it as the go-tops-baseline artifact; it is committed unchanged in the next commit.
The ledger is the go-tops-baseline artifact of the first pull request run, committed byte for byte. It was written by the ledger leg (the ubuntu leg of the gate job) on its own build: linux/amd64, cgo on, no tags. It records 8 functions over the CRAP cap of 10, no package under the 75% statement floor, 64 lint findings under the Go-TOPS lint rules in 15 files, and no suppressions or exemptions.
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.
Adopt Go-TOPS: a
gatejob besidecheck, classbinary-service.This adds the Go-TOPS gate under
enforce: ratchet. vigil's owncheckjob,.golangci.yml,ci.yml,go.modandgo.sumare unchanged, andcheck (ubuntu-latest)andcheck (macos-latest)stay the required checks.go-tops.yamlandgo-tops.lock;tools/go.modandtools/go.sumpingotopsatv0.0.0-20261119162302-608716388245, a pseudo-version of go-topsmain(no tag, no replace)..github/workflows/go-tops.yml: thegatejob with ubuntu, macOS and floor legs, under its own name and concurrency group..go-tops/golangci.yml: the lint rules the gate reads. The repository's own.golangci.ymlis not read by the gate.GO-TOPS.md, theAGENTS.mdblock,justfile,CODEOWNERSand a marked.gitignoreblock.The first ledger. No ledger is committed yet. On this pull request the ubuntu leg (the ledger leg) finds that a first ledger is due, writes it on its own build, uploads it as the
go-tops-baselineartifact, and fails the run on purpose. The ledger is then committed unchanged in the next commit, and the next run judges the ratchet against it. The ledger records vigil's current debt under the kit's rules; it can only be lowered.Not in this PR: making
gatea required check. That is a ruleset change, considered after two weeks of green runs.Merged with a merge commit.
🤖 Generated with Claude Code