vladopajic/go-test-coverage@v2 (v2.18.5+, released 2026-04-26/27) restructured its composite action to pass inputs via env-var mapping. Gitea act_runner doesn't expand ${{ }} expressions inside docker-action env: blocks reliably, so the literal string ${{ inputs.config }} reached the binary and broke the 'Check coverage' step.
Replace the action with a direct go install + binary invocation (matching the established Frostmoln pattern).
Use --github-action-output to expose total-coverage as a step output, replacing the manual go tool cover -func | grep | awk calculations.
Baseline artifact now stores the percentage directly instead of the full coverage profile.
Bump go directive in go.mod from 1.24.4 → 1.26.2 (matching toolchain) — we are the sole consumers of this module.
Test plan
prek run --all-files passes
CI passes on this PR
After merge, baseline artifact format propagates on next push to main
## Summary
- `vladopajic/go-test-coverage@v2` (v2.18.5+, released 2026-04-26/27) restructured its composite action to pass inputs via env-var mapping. Gitea `act_runner` doesn't expand `${{ }}` expressions inside docker-action `env:` blocks reliably, so the literal string `${{ inputs.config }}` reached the binary and broke the 'Check coverage' step.
- Replace the action with a direct `go install` + binary invocation (matching the established Frostmoln pattern).
- Use `--github-action-output` to expose `total-coverage` as a step output, replacing the manual `go tool cover -func | grep | awk` calculations.
- Baseline artifact now stores the percentage directly instead of the full coverage profile.
- Bump `go` directive in `go.mod` from 1.24.4 → 1.26.2 (matching toolchain) — we are the sole consumers of this module.
## Test plan
- [x] `prek run --all-files` passes
- [ ] CI passes on this PR
- [ ] After merge, baseline artifact format propagates on next push to main
vladopajic/go-test-coverage@v2 (v2.18.5+) restructured the composite
action to pass inputs via env-var mapping. Gitea act_runner does not
expand expressions in those blocks, so the literal string
'${{ inputs.config }}' reached the binary, breaking the coverage step.
Replace the action with a direct go install + binary invocation
(matching the Frostmoln pattern) and use --github-action-output to
expose total-coverage as a step output, dropping manual
'go tool cover -func' calculations.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
vladopajic/go-test-coverage@v2(v2.18.5+, released 2026-04-26/27) restructured its composite action to pass inputs via env-var mapping. Giteaact_runnerdoesn't expand${{ }}expressions inside docker-actionenv:blocks reliably, so the literal string${{ inputs.config }}reached the binary and broke the 'Check coverage' step.go install+ binary invocation (matching the established Frostmoln pattern).--github-action-outputto exposetotal-coverageas a step output, replacing the manualgo tool cover -func | grep | awkcalculations.godirective ingo.modfrom 1.24.4 → 1.26.2 (matching toolchain) — we are the sole consumers of this module.Test plan
prek run --all-filespassesvladopajic/go-test-coverage@v2 (v2.18.5+) restructured the composite action to pass inputs via env-var mapping. Gitea act_runner does not expand expressions in those blocks, so the literal string '${{ inputs.config }}' reached the binary, breaking the coverage step. Replace the action with a direct go install + binary invocation (matching the Frostmoln pattern) and use --github-action-output to expose total-coverage as a step output, dropping manual 'go tool cover -func' calculations.Coverage Report
Total coverage: 100%