chore: updates coverage GH action to compare coverage against base branch - #28
Closed
0xItadaki wants to merge 21 commits into
Closed
chore: updates coverage GH action to compare coverage against base branch#280xItadaki wants to merge 21 commits into
0xItadaki wants to merge 21 commits into
Conversation
0xItadaki
marked this pull request as ready for review
August 26, 2025 12:54
LCOV of commit
|
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.
1- When the PR is created, it runs the coverage in the base branch and caches result

2- With every push it calculates the coverage in the current PR and creates a comment with coverage information. This comment is updated every time there is a new push.
3- It compares the total coverage from the base branch and the new push. If the coverages decreases in the new push, a the comment is updated and the build fails
Note: yarn coverage only runs unit tests to avoid killing the RPC with fuzz tests
Note: It uses a sensitivity factor, otherwise the coverage fails even if nothing changes.