Troubleshooting code scanning
When analyzing your code with code scanning, you may need to troubleshoot unexpected issues.
When analyzing your code with code scanning, you may wish to build only the code which you wish to analyze.
If automatic build fails, you can configure code scanning to use specific build steps for compiled languages.
You can fine tune CodeQL to minimize analysis time.
If CodeQL analyzed less code than than you expected, you may need to use a custom build command.
You can check whether or not extraction errors affect the health of the CodeQL database created.
If you'd like to increase the level of detail in your logs, try these steps.
When CodeQL fails to find any source code, you need to resolve this problem to unblock code scanning analysis.
CodeQL was unable to locate one of the queries or sets of queries that are specified for analysis.
If you see one of these errors with GitHub Actions, try reviewing the specifications of your self-hosted runners.
If some languages were not analyzed, you can modify your code scanning workflow to add a matrix specifying the languages you want to analyze.
If you see this warning, you should update your workflow to follow current best practice.