-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always run coverage against base #1662
Merged
Merged
Conversation
This file contains 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
Open to requiring that forge coverage never decrease, wdyt? |
yorhodes
approved these changes
Jan 25, 2023
Forge Coverage ReportCoverage after merging asaj/coverage into main will be
Coverage Report
|
Hardhat Coverage ReportCoverage after merging asaj/coverage into main will be
Coverage Report |
Closed
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.
Description
This PR modifies our github actions to always run coverage against the base branch.
This workflow assumes the existence of a cached
solidity/coverage
directory keyed by the sha of the base branch. If no cache entry is found, the workflow will failBecause there won't be a cache entry for main, we hacked around this by temporarily committing the current coverage artifacts, which causes the caching action to cache those as if they were the values on main. They were then removed.
This workflow is also updated to fail iff both hardhat and forge coverage decrease.
Drive-by changes
Related issues
Backward compatibility
Yes
Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?
None
Testing
Manual - running the action