fix(ci): use go-test-coverage binary directly to fix Gitea Actions #88

Merged
argoyle merged 1 commits from fix/coverage-tool-binary into main 2026-04-29 05:44:55 +00:00
Owner

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

  • 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
argoyle added 1 commit 2026-04-29 05:06:53 +00:00
fix(ci): use go-test-coverage binary directly to fix Gitea Actions
dbsetup / vulnerabilities (pull_request) Successful in 2m19s
dbsetup / test (pull_request) Successful in 2m31s
pre-commit / pre-commit (pull_request) Successful in 7m20s
ba5169db69
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.

Coverage Report

Total coverage: 0%

## Coverage Report Total coverage: **0%**
argoyle merged commit bdff36b446 into main 2026-04-29 05:44:55 +00:00
argoyle deleted branch fix/coverage-tool-binary 2026-04-29 05:44:56 +00:00
Sign in to join this conversation.
No Reviewers
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/dbsetup#88