Skip to content

Replace Codecov with Qlty for coverage reporting#847

Closed
davehenton wants to merge 1 commit intosamber:masterfrom
dh-sandbox:qlty-coverage-integration
Closed

Replace Codecov with Qlty for coverage reporting#847
davehenton wants to merge 1 commit intosamber:masterfrom
dh-sandbox:qlty-coverage-integration

Conversation

@davehenton
Copy link

Summary

  • Replaced Codecov upload step with Qlty coverage action (qltysh/qlty-action/coverage@v2) in the test workflow
  • Coverage data is generated by the existing make coverage step (go test -coverprofile=cover.out) on the stable Go version
  • Uses token-based authentication (public repo)

Manual steps required

  1. Add a QLTY_COVERAGE_TOKEN secret to this repository's GitHub Actions secrets
    • Generate the token from Qlty Cloud project settings
    • Go to Repository Settings → Secrets and variables → Actions → New repository secret
    • Name: QLTY_COVERAGE_TOKEN, Value: your Qlty coverage token

Test plan

  • Add QLTY_COVERAGE_TOKEN secret to the repo
  • Verify the Tests workflow passes on this PR
  • Confirm coverage data appears in Qlty Cloud dashboard

🤖 Generated with Claude Code

Swap the Codecov upload step for the Qlty coverage action in the
test workflow. Coverage is generated from the existing `make coverage`
step (Go cover profile) and uploaded via qltysh/qlty-action/coverage@v2
using a coverage token.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@davehenton davehenton closed this Mar 18, 2026
@davehenton davehenton deleted the qlty-coverage-integration branch March 18, 2026 19:46
@samber samber added the spam Contain irrelevant, low-quality, promotional, or abusive content not related to the project. label Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

spam Contain irrelevant, low-quality, promotional, or abusive content not related to the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants