stacklok / toolhive-studio / 24564436689

63%

main: 71%

Pull #2036

github

fix(ci): pin Coveralls git-commit to PR head to dedupe status posts

On pull_request events GitHub runs the workflow against a temporary merge SHA (refs/pull/N/merge), and `coverallsapp/github-action` auto-detects the commit from $GITHUB_SHA. Coveralls then registers a build against the merge SHA in addition to the PR head SHA, producing two `coverage/coveralls` status posts on the same PR head commit (two different coveralls.io/builds/<id> URLs, 2–3 minutes apart) — see PR #2032 where `builds/78939336` and `builds/78939464` both landed on the same SHA. Root cause and fix documented in lemurheavy/coveralls-public#1739.

Explicitly set `git-commit` to `github.event.pull_request.head.sha` on pull_request events and fall back to `github.sha` on push (used by on-main.yml). Also set `git-branch` to `github.head_ref` on PRs (falling back to `github.ref_name`) so the Coveralls build card shows the real source branch instef `refs/pull/N/merge`. The workflow is called from both on-pr.yml (pull_request) and on-main.yml (push), and the expressions resolve correctly in both: on pull_request, `github.event.pull_request.head.sha` is populated and `github.head_ref` is the source branch; on push, both fall back to `github.sha` / `github.ref_name` respectively.

3575 of 5980 branches covered (59.78%)

5705 of 8708 relevant lines covered (65.51%)

120.41 hits per line