Closed thaJeztah closed 2 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 61.07%. Comparing base (
e81b835
) to head (e3216ca
).
Thx! FWIW; not 100% sure this will fix the issues, but it started to show errors / warnings, and looking at the logs, these were the ones that I found. It didn't fail though, so 🤷♂️
Looks like there's still some warnings / errors; one of them looks to be related to https://github.com/docker/cli/pull/4624, which renamed the workflow file; I can try deleting the workflow from that page;
The other one is that it's still complaining about go files that it didn't analyse. Wondering if that's mac <--> windows, or something else;
Hmm... right, so it shows more now on that page;
And it provides a CSV to show what files were analysed and what ones weren't...
code-scanning-files-extracted.csv
And from the looks of it;
_test.go
fileswindows
filesSo not sure if (at least) _test.go
files could be enabled for it (but it's funny that it's effectively imposing a penalty for having tests 😂), and don't know if it supports windows;
gha: CodeQL: move go.mod/go.sum symlink earlier to help caching
actions/setup-go was trying to use caching, and produced a warning because it expects a
go.mod
/go.sum
;While our regular builds would use a containerised flow, CodeQL's autobuild does not, and also doesn't seem to use our vendor directory (?) so for this one it's probably fine to let it use some caching.
go.mod: use SemVer format for go version to assist CodeQL AutoBuild
CodeQL AutoBuild started to produce errors if the
go.mod
does not use SemVer for the go version; https://github.com/github/codeql/blob/3a2b0a2feba58c05706c88b5589cacf6094f7f9d/go/extractor/diagnostics/diagnostics.go#L512-L525Let's give it one.