Use proper finding IDs for sonar and semgrep SARIF #956
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
drdavella
force-pushed
the
fix-sonar-finding-id
branch
from
ded2f70 to
7a40b51
Compare
andrecsilva
approved these changes
Dec 19, 2024
drdavella
force-pushed
the
fix-sonar-finding-id
branch
from
7a40b51 to
b0bb653
Compare
drdavella
force-pushed
the
fix-sonar-finding-id
branch
from
b0bb653 to
3999240
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Use unique finding IDs (where available) for results from Sonar JSONs and Semgrep SARIF