fix: Setup custom codeQL with the latest codeql-actions. #162
+53
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently we have started to see the failures of javascript/typescript check of CodeQL: here is one example.
The issue happens because the action
github/codeql-action/analyze@v3does not set the variable toCODEQL_EXTRACTOR_ACTIONS_WIP_DATABASE, which is needed by the new version of CodeQL binary to analyse the GitHub actions. This results in warning and consequent failure to finalize the database: CodeQL detected code written in JavaScript/TypeScript but could not process any of it.There are two possible soilutions:
CODEQL_EXTRACTOR_ACTIONS_WIP_DATABASE(this PR).defaultCodeQL scenario (set through GitHub UI) and disable javascript check as we do not have the java script code in this repository.I have checked the fix on the forked repository.
This change is