Private Preview: Code Coverage — Native Test Coverage in Pull Requests

[AlonaHlobina]

TL;DR

We're excited to invite a select group of customers to the Private Preview of Code Coverage — a native GitHub feature that brings test coverage results directly into your pull request experience. No third-party tool required.

If you're part of this preview, you can start using Code Coverage today by adding a simple step to your test workflow.

🎯 Why Code Coverage?

Code coverage is one of our most requested features. Many teams rely on third-party tools like Codecov, Coveralls, or SonarQube to get coverage signals — but that means context-switching, extra configuration, and fragmented workflows.

Code Coverage brings test coverage directly into the PR experience so your team can:

• ✅ Make faster, higher-confidence merge decisions — see at a glance whether changes are tested
• 🔍 Spot risky, untested changes before they reach production
• 🎯 Prioritize review attention on the areas that matter most
• 🔄 Reduce context-switching — no more jumping to a separate coverage product

👀 What You'll See

When you open a pull request on an enrolled repository, you'll see a coverage summary in the PR experience showing the overall coverage percentage. This gives reviewers a quick signal about whether changes are tested.

Note: During this phase, coverage results appear as a high-level summary (e.g., overall percentage). Line-by-line annotations within the diff view are planned for a future release.

🔧 How it works

1. You add the coverage generation+upload to a new or existing workflow that runs a test suite and produces a report in Cobertura XML format (most frameworks support this natively or via conversion — e.g., JaCoCo → Cobertura for Java, Istanbul/nyc for JS, gocover-cobertura for Golang).
2. The coverage summary will appear automatically

Example repository with a working workflow: 👉 https://github.com/code-quality-org/joshhale-code-coverage-workflow
Check out the extensive instructions for setup : 👉 https://gist.github.com/AlonaHlobina/d1a2acad7960e08e9199fe61b2ced7ea

✅ What's Included / 🚧 What's Not Yet

	Status
✅ PR coverage summary	Available now
✅ Upload via API endpoint	Available now
✅ Any language (Cobertura XML)	Available now
✅ First-party GitHub Action for upload	Available now
🚧 Merge blocking / coverage thresholds	Planned for Public Preview
🚧 Historical trend tracking	Planned for future release
🚧 Line-by-line diff annotations	Planned for future release

🗣️ How to Give Feedback

• We want your feedback! Here's what we're especially interested in:
• 📊 PR signal usefulness — Is the coverage summary helpful for review decisions?
• 🔮 What you'd need next — What's missing for this to become part of your daily workflow?
• Bug reports

Ways to share:

Channel	Use for
↩️ Reply to this discussion	General feedback, impressions, screenshots, questions

Thank you for helping us validate Code Coverage before we bring it to customers. Your feedback directly shapes the product — don't hold back! 🚀

[beingminimal]

@AlonaHlobina We’d be delighted to begin using this feature and provide feedback. Could you please enable this feature for the following organisation on GitHub? We eagerly await your response. Thanks!

CodecycleLLP
MahakaalGH
StaytunedFoundation
StaytunedLAB
StaytunedLLP
Z1-Test
Z2-Test

[carogalvin]

@AlonaHlobina no

[beingminimal]

@AlonaHlobina no

Any hope?

[AlonaHlobina]

This isn't currently on our roadmap as we're focusing on other priorities. However, we've noted your request and will keep it on our radar.

[beingminimal]

@AlonaHlobina How this feature is supporting typescript & node test runner and how we can inject coverage report when we use our inhouse library of test like jest or mocha?

[coadaflorin]

Hey @beingminimal , to get some clarity and guide you in the right direction. What do you mean by our inhouse library of test like jest or mocha?
If you're using jest/moch in your actions config you can run the tests, then use Istanbul to convert your coverage reports to cobertura.xml which is the only format support right now.

If you have your own in house test library, the process would be similar, but you'll need to find a way to convert the reports you generate to cobertura.xml

[jrwdexter]

@AlonaHlobina we would also love to start using this feature & provide feedback! This would be our first time using a preview feature, so let us know what steps would be necessary to enable it for our organization, Monkeyjump-Labs

Thank you!

[AlonaHlobina]

Your org has been added to the private preview. Please follow the instructions to set it up: https://gist.github.com/AlonaHlobina/d1a2acad7960e08e9199fe61b2ced7ea

[hfhbd]

I also would like to test it out, with this personal account.

I guess, the preview is not yet available at GHE with data residency (EU)?