wow-look-at-my/Go Safe Build

Build Go projects with coverage enforcement - fails if coverage is below threshold

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
jsonOutput coverage report as JSONnofalse
generateRun go:generate directives matching this hashno""
working-directoryWorking directory for the buildno.
binaryPath to a pre-built go-toolchain binary (skips release download)no""
osComma-separated list of target operating systems (e.g. linux,darwin,windows)nolinux,darwin,windows
archComma-separated list of target architectures (e.g. amd64,arm64)noamd64,arm64
targetsComma-separated exact build targets, each an os/arch pair (e.g. darwin/amd64) or the special value "cosmo" (one fat APE built with the gosmopolitan toolchain, plus per-platform slot copies). When non-empty this replaces the os/arch inputs.no""
cgoEnable CGO (disabled by default for static binaries)nofalse
autoreleaseAutomatically publish to buildhost on every branch push (requires id-token: write permission; with deployments: write it also registers a GitHub Deployment, skipped with a warning otherwise)notrue
autorelease_argsExtra publish options forwarded to the buildhost publish, as whitespace- or comma-separated key=value pairs (e.g. "create_service=true"). Recognized keys: create_service (true|false -- declare that the published binary runs as a background service; each download format materializes it, e.g. brew formulas gain a `service do` block and generated debs ship an auto-enabled systemd user unit). Unknown keys fail the build. Empty (the default) forwards nothing -- the publish request is byte-identical to before this input existed.no""
allow-source-buildAllow building go-toolchain from source when the buildhost binary is unavailable. When false (default), the build fails fast instead of silently falling back to a source build.nofalse
timeoutTimeout in minutes for the go-toolchain build stepno10
wait-ciWait for the latest go-toolchain CI run to finish before downloading the release binarynofalse
codeqlRun CodeQL security-and-quality analysis around the build (requires security-events: write permission, and the consumer repo must NOT have GitHub default CodeQL setup enabled)nofalse

no outputs