vladopajic/go-test-coverage@v2 (v2.18.5+, released 2026-04-26/27) restructured the composite action to pass inputs via env-var mapping instead of CLI args. 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 the tool's --github-action-output to expose total-coverage as a step output, replacing the manual go tool cover -func | grep | awk calculations in the compare and PR-comment steps.
Baseline artifact now stores the percentage directly instead of the full coverage profile.
Test plan
pre-commit 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 the composite action to pass inputs via env-var mapping instead of CLI args. 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 the tool's `--github-action-output` to expose `total-coverage` as a step output, replacing the manual `go tool cover -func | grep | awk` calculations in the compare and PR-comment steps.
- Baseline artifact now stores the percentage directly instead of the full coverage profile.
## Test plan
- [x] `pre-commit 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+) switched composite-action
inputs from CLI args to env-var mapping, which Gitea act_runner does
not expand reliably. The literal string `${{ inputs.config }}` was
passed to the binary, breaking 'Check coverage' steps.
Replace the action with a direct go install + binary invocation
(matching Frostmoln pattern) and use the tool's --github-action-output
to drop 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 the composite action to pass inputs via env-var mapping instead of CLI args. 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 in the compare and PR-comment steps.Test plan
pre-commit run --all-filespassesvladopajic/go-test-coverage@v2 (v2.18.5+) switched composite-action inputs from CLI args to env-var mapping, which Gitea act_runner does not expand reliably. The literal string `${{ inputs.config }}` was passed to the binary, breaking 'Check coverage' steps. Replace the action with a direct go install + binary invocation (matching Frostmoln pattern) and use the tool's --github-action-output to drop manual go tool cover -func calculations.Coverage Report
Total coverage: 0%