-
Notifications
You must be signed in to change notification settings - Fork 315
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
1 files were completely excluded from scanning due to a fundamental problem that is known to cause problems scanning other files. #2258
Comments
The cause is that you're running a build (note the |
Thank you for the info. I just replaced the autobuild step that was initially suggested, which was not working for me, with the build step I am using. Is the build step actually needed by CodeQL or does it only analyze the source code? I mean, is adding a build on top of it adding any further value? |
It depends on the The particular oddity seen here results from the unexpected combination of |
I created a new test repository for setting up various github actions. The repository itself does not have real important code other than to demonstrate various things like a functioning build-pipeline even in case of module usage and such. The task I was given is to create releases to Maven Central on manual tags rather than to rely on the default release cycle.
While investigating into CodeQL action, I noticed that a warning is popping up during the
Perform CodeQL Analysis
step of the pipeline.The exact message here reads as:
The warning is not really helpful at all as I can't really determine which file it is referring to even though this repo only has a handful of files. Not sure how much of an effort it would be to at least list the files that CodeQL is complaining about would be a sane thing IMO. The reported problem seems also a bit strange as there is a
module-info.java
file that declares a Java module. Which other file should there be that "declares" a module but is not within amodule-info-java
file?The text was updated successfully, but these errors were encountered: