Fix coverage report #9
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
The commit modifies the trigger event for the coverage workflow in Github actions. Instead of triggering on push events, it now triggers on pull request events. This affects both the 'main' and 'beta' branches as defined in coverage.yaml.
Coverage report
Test suite run success63 tests passing in 1 suite. Report generated by 🧪jest coverage report action from 8e143fd |
|
🎉 This PR is included in version 1.3.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 coverage repost suppose to happen once a PR is raised. But it happens after a push is made to the main/beta branch there by not giving us metrics on the quality of the PR.
This PR is a fix for that which forces it to generate coverage on every PR.