fix: Include artifact locations in SARIF reports #204
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
This should allow them to be uploaded to GitHub. Fixes #197
|
ping @tomoyamachi |
|
@twelvelabs Thank you for your contribution! |
|
The merged code is released as Dockle v0.4.9. |
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.
Fixes #197.
I'm not a SARIF expert, but I followed the info at https://github.com/microsoft/sarif-tutorials and I think this should be correct. I also installed the SARIF viewer VS Code extension and confirmed that the fixture files were showing up as expected:
Note: the
-in the line column is because we're not including a line number in the location (I didn't see that data in theAssessmentstruct).