[Bug] Update report json schema for git branch information #914
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
Signed-off-by: Wei-Chun, Chang <[email protected]>
wcchang1115
changed the title
Codecov Report
@@ Coverage Diff @@
## main #914 +/- ##
=======================================
Coverage 48.00% 48.01%
=======================================
Files 78 78
Lines 10751 10751
=======================================
+ Hits 5161 5162 +1
+ Misses 5590 5589 -1 see 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
qrtt1
approved these changes
Oct 25, 2023
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.
PR checklist
What type of PR is this?
bug
What this PR does / why we need it:
v0.34.0,git_branchinformation in a run report could be null when compared with git references other than branches.Which issue(s) this PR fixes:
sc-32458
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE