@gregkh oh here is how you ignore specific paths https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning#specifying-directories-to-scan
Notices by tbodt (tbodt@mastodon.social)
-
Embed this notice
tbodt (tbodt@mastodon.social)'s status on Saturday, 16-Nov-2024 17:38:31 JST tbodt
-
Embed this notice
tbodt (tbodt@mastodon.social)'s status on Saturday, 16-Nov-2024 17:38:21 JST tbodt
@gregkh your last toot showed errors in meson generated files so maybe delete the Build step from the codeql workflow? i'm not sure why exactly you'd want that in static analysis. though there must be some reason the original author put it there so i'm not too sure either way.
In conversation from mastodon.social permalink -
Embed this notice
tbodt (tbodt@mastodon.social)'s status on Saturday, 16-Nov-2024 16:49:20 JST tbodt
@gregkh @captainepoch this is probably only visible to repo admins (because security issues shouldn't be disclosed publicly or something). also i did a quick web search and found the docs https://docs.github.com/en/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning
In conversation from mastodon.social permalink Attachments
-
Embed this notice
tbodt (tbodt@mastodon.social)'s status on Saturday, 16-Nov-2024 16:49:19 JST tbodt
@gregkh @captainepoch oh here is where it got configured https://github.com/gregkh/usbutils/commit/15f33f0dc49ec58c8761fa33da2afc0486164610
In conversation from mastodon.social permalink Attachments
-
Embed this notice
tbodt (tbodt@mastodon.social)'s status on Friday, 13-Sep-2024 12:21:57 JST tbodt
@zarfeblong i have a feeling this could only mean they are going to form a new publishing company and rehire everyone
In conversation from mastodon.social permalink