Repository navigation
Conversation
…be, do not merge)
Collaborator
Author
|
Probe answered: comment-only touches of these six files raise no new alerts, so the #1102 CodeQL findings come from its changed macro-generated launch code being re-fingerprinted, not from merely touching the files. Closing. |
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.
Comment-only touches of the six example files whose pre-existing kernel code CodeQL flags on #1102. If this PR's CodeQL check passes, the alerts are already in main's baseline and #1102's failures are attribution artifacts of the large diff; if it fails with the same alerts, the PR gate attributes them to any PR touching these files. Will be closed once the check reports.