Repository navigation
chore(harness): update the harness to v0.1.28 - #30
Merged
Merged
Conversation
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.
Moves the harness to v0.1.28: the reusable workflow (
@v0.1.28) and thepollora/harnessconstraint (^0.1.28).v0.1.28 adds
mutation.scope: "changed"to.harness.json(the mutation gate limited to the files a change touches, for a repository whose whole mutation run is too long for CI) andcheck --mutation-base; it also stops reading a file without any mutant as a score of 0 %. The versions since 0.1.24 enforce SEC-01 and ARCH-05, runcheck --mutationfor a repository that recordedratchet.msi, and fix thepcov.directoryscope. No change to the code of this repository; the ratchet in.harness.jsonis left as it is, and this repository's own mutation gate (if it has one) behaves as before.