Add verify script that replaces the code coverage workflow - #550
Merged
Conversation
Contributor
|
Commit 81665b8 |
MartinKl
enabled auto-merge
August 17, 2026 11:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This removes our dependency to the external Codecov service and allows to measure the code coverage of the PR/patch before submitting it locally.
To use the
verify.shscript locally, you have to install diff-cover first:The
verify.shscript is adapted from graphANNIS and also executes all tests, checks that the code is formatted and runs clippy.For PRs that are submitted from this repo, a comment will be added with the code coverage information.
The comment is only text, but if you run the script locally you get a nice HTML page with the changed lines and their coverage information.
Adding a comment to the PR is skipped for PRs from fork because of GitHub Actions security guard rails. The script is still run and would fail if the minimal patch coverage (80%) is not reached and the output is visible in the logs.