Report the scan delta on the pull request and job summary#10
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.
Until now the only place a reader could see what a scan found was the raw CI log. Every run now renders a markdown report — new findings with severity,
file:lineand a link to the task each one created — and publishes it:pull-requests: write; without it the report simply stays in the summary.The report is published before the gate exits, because a failed gate is exactly when the detail is needed. A baseline scan is framed as such — findings recorded, no work created, nothing gated.
Pairs with startmatter/k#337, which adds
taskKey(SID/T/12) andtaskUrlto the ingest response so the report can link to the work rather than print an opaque id.