Skip to content

ci(workflows): add coverage test job to PR checks#1369

Merged
piorpua merged 1 commit intomainfrom
feat/ci-coverage-tests
Mar 17, 2026
Merged

ci(workflows): add coverage test job to PR checks#1369
piorpua merged 1 commit intomainfrom
feat/ci-coverage-tests

Conversation

@loonghao
Copy link
Copy Markdown
Collaborator

@loonghao loonghao commented Mar 17, 2026

Background

The current PR Checks pipeline runs code quality checks, unit tests, and build validation, but it does not have a dedicated coverage job. This PR adds a coverage CI step so coverage results are explicitly validated during PR checks and used as a prerequisite for downstream AI review jobs.

Changes

  • Added a new coverage-tests job in .github/workflows/pr-checks.yml (runs on ubuntu-latest)
  • Executes bun run test:coverage
  • Uploads coverage artifacts from coverage/ (artifact name: coverage-report)
  • Updated downstream job dependencies:
    • review now depends on coverage-tests
    • check-external now depends on coverage-tests
  • Workflow-only change; no application/business logic modified

Impact

  • File changed: .github/workflows/pr-checks.yml
  • PR validation flow now includes a dedicated coverage step
  • Coverage artifacts can be downloaded from the PR workflow run
  • AI review/assessment jobs only run after coverage succeeds

Verification

  • Workflow YAML was formatted with Prettier
  • Branch has been pushed and PR is ready for CI validation

@loonghao loonghao changed the title ci(workflows): add coverage test job to PR checks ci(workflows): 增加 PR 覆盖率测试任务 Mar 17, 2026
@loonghao loonghao changed the title ci(workflows): 增加 PR 覆盖率测试任务 ci(workflows): add coverage test job to PR checks Mar 17, 2026
@piorpua piorpua merged commit f8fc0eb into main Mar 17, 2026
31 of 39 checks passed
@piorpua piorpua deleted the feat/ci-coverage-tests branch March 17, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants