Write findings as SARIF for code scanning - #1
Merged
Merged
Conversation
sarif-file replays the check from the answers it just cached with --format sarif, so it costs nothing, and the README shows uploading it with upload-sarif. Needs JevGate 0.18.0 or later.
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
1 participant
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.
sarif-file: after the check, the action runs it again with--cache-only --format sarif, replaying the answers it just cached (no request is sent), and writes the SARIF log to that path. A replay that fails (such as an older JevGate) is a warning, not a failed step; the check's own exit code is unchanged.--formatis given once each.github/codeql-action/upload-sarif@v4(if: always(),category: jevgate,security-events: write), and the new formats in the inputs table.Checked locally with a JevGate build that has
--format sarif: the check's exit code and outputs are unchanged, and the file is a valid SARIF 2.1.0 log.