Repository navigation
chore: run the Harness on develop and record the line coverage - #10
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.
The Harness workflow only listed
mainunderpush, andmaindoes not have the file yet (it lives ondevelop), so it has never run on a push: only on pull requests. The nightlyscheduledoes not run either, since a schedule only fires from the default branch.pushnow listsdeveloptoo, so the Harness runs on each merge intodevelop..harness.jsonrecordscoverage: 74.41, the line coverage the Harness measures on the pull requests (recorded - measured 74.41 new), so it can no longer fall unnoticed (tolerance 0.05 point).The schedule starts once
harness.ymlreachesmain, with the nextdeveloptomainpull request..harness.jsonis protected (QA-02): this change was decided by the owner.