Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: codeql ignore meson generated files, et al #211

Merged
merged 3 commits into from
Nov 16, 2024

Conversation

evelikov
Copy link
Contributor

Hey Greg, here's a quick PR to silence most of the CodeQL dubious reports. I've also added a couple more CI commits just to keep you on your toes ;-)

lucasdemarchi and others added 3 commits November 16, 2024 10:26
Make sure we are running in non-interactive mode and that we don't get
blocked on tzdata update.

Signed-off-by: Lucas De Marchi <[email protected]>
[Emil: port from kmod]
Signed-off-by: Emil Velikov <[email protected]>
There's no need to manually create and cd into the build directory,
since meson knows how to handle that.

Signed-off-by: Emil Velikov <[email protected]>
There is a severe number of false-positive in code scanning caused by
inspecting meson-internal test files like
'build/meson-private/tmpzb46osmq/testfile.c'.

As a workaround, use the 'filter-sarif' action to filter out these
results before uploading the SARIF (Static Analysis Results Interchange
Format).

This PR was inspired by rauc/rauc#1346 and the
example from https://github.com/advanced-security/filter-sarif.

Signed-off-by: Enrico Joerns <[email protected]>
[Emil: port from rauc, use checksums for actions]
Signed-off-by: Emil Velikov <[email protected]>
@gregkh
Copy link
Owner

gregkh commented Nov 16, 2024

Thank you so much!

@gregkh gregkh merged commit 79a0b23 into gregkh:master Nov 16, 2024
16 checks passed
@evelikov evelikov deleted the codeql-tidy branch November 16, 2024 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants