Create separate path for CI reports #1334
Open
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
sushantmane
reviewed
Nov 21, 2024
| @@ -52,9 +52,11 @@ jobs: | |||
| - name: Publish Test Report | |||
| env: | |||
| NODE_OPTIONS: "--max_old_space_size=4096" | |||
| uses: mikepenz/action-junit-report@v3 | |||
There was a problem hiding this comment.
IMO this has to be right after
Run Unit Tests & Code Coverage
If we want to run it on failure only
sushantmane
reviewed
Nov 21, 2024
|
Instead of check can we always use annotations always? This way we will have results on prs, post commits, and forks? |
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.
Create separate path for CI reports
Show CI report for different modules in different links.
How was this PR tested?
Does this PR introduce any user-facing changes?