GitHub just made code coverage visible inside pull requests through GitHub Code Quality, now in public preview.
That sounds like a small UI update, but it changes a common review problem: reviewers often approve code without knowing whether the new path is tested at all. If coverage is available directly in the PR, the conversation moves from vague “please add tests” comments to a clearer signal: what changed, what is covered, and what should we block before merge?
This post breaks down what shipped, why it matters, and how to wire it into a real GitHub Actions workflow.
What changed?
GitHub Code Quality can now show an aggregate code coverage percentage directly on pull requests.
