unboundsoftware/pagination
6
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 7 Activity

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

Merged
argoyle merged 2 commits from fix/coverage-tool-binary into main 2026-04-29 06:09:53 +00:00
Conversation 1 Commits 2 Files Changed 2
+12 -16
argoyle commented 2026-04-29 05:17:29 +00:00
Owner
Copy Link
Copy Source

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

  • 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
argoyle added 1 commit 2026-04-29 05:17:30 +00:00
fix(ci): use go-test-coverage binary directly to fix Gitea Actions
pagination / vulnerabilities (pull_request) Failing after 1m38s
Details
pagination / test (pull_request) Failing after 2m17s
Details
pre-commit / pre-commit (pull_request) Successful in 5m17s
Details
967e0ae1f1 
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.
argoyle added 1 commit 2026-04-29 05:47:28 +00:00
chore(deps): bump go directive to 1.26.2
pagination / vulnerabilities (pull_request) Successful in 1m45s
Details
pagination / test (pull_request) Successful in 2m49s
Details
pre-commit / pre-commit (pull_request) Successful in 6m4s
Details
4c34b45b2a 
Match toolchain version. We are the sole consumers of this module.
argoyle scheduled this pull request to auto merge when all checks succeed 2026-04-29 06:05:38 +00:00
gitea-actions bot commented 2026-04-29 06:06:00 +00:00
Copy Link
Copy Source

Coverage Report

Total coverage: 100%

## Coverage Report Total coverage: **100%**
argoyle merged commit 557abf0540 into main 2026-04-29 06:09:53 +00:00
argoyle deleted branch fix/coverage-tool-binary 2026-04-29 06:09:55 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acctest (Shiny Acctest) argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/pagination#96
Delete Branch "fix/coverage-tool-binary"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?