Code Scanning selectors: Include diagnostic queries #5914
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the code scanning selectors to include diagnostic queries like extractor error messages. This will mean we start analyzing these queries on Code Scanning by default.
This PR should not be merged until the next CLI release, since diagnostic queries cannot be interpreted using the current CLI release and will causecodeql database analyzeto fail.This PR is a breaking change for users running the latest query suite in
mainwith a non-bleeding-edge CLI. Users using v2.5.5 of the CLI or earlier will need to instead use the query suite from the2.5.5tag: https://github.com/github/codeql/releases/tag/codeql-cli%2Fv2.5.5.