This content describes the most recent release of the CodeQL CLI. For more information about this release, see https://github.com/github/codeql-cli-binaries/releases.
To see details of the options available for this command in an earlier release, run the command with the
--help option in your terminal.
codeql resolve languages <options>...
List installed CodeQL extractor packs.
When run with JSON output selected, this command can report multiple locations for each extractor pack name. When that happens, it means that the pack has conflicting locations within a single search element, so it cannot actually be resolved. The caller may use the actual locations to format an appropriate error message.
A list of directories under which extractor packs may be found. The directories can either be the extractor packs themselves or directories that contain extractors as immediate subdirectories.
If the path contains multiple directory trees, their order defines precedence between them: if the target language is matched in more than one of the directory trees, the one given first wins.
The extractors bundled with the CodeQL toolchain itself will always be
found, but if you need to use separately distributed extractors you need
to give this option (or, better yet, set up
--search-path in a
per-user configuration file).
(Note: On Windows the path separator is
Select output format. Choices include:
text (default): Print the paths to extractor packs to standard
json: Print the paths to extractor packs as a JSON string.
betterjson: Print details about extractor packs as a JSON string.
Show this help text.
[Advanced] Give option to the JVM running the command.
(Beware that options containing spaces will not be handled correctly.)
Incrementally increase the number of progress messages printed.
Incrementally decrease the number of progress messages printed.
[Advanced] Explicitly set the verbosity level to one of errors,
warnings, progress, progress+, progress++, progress+++. Overrides
[Advanced] Write detailed logs to one or more files in the given directory, with generated names that include timestamps and the name of the running subcommand.
(To write a log file with a name you have full control over, instead
--log-to-stderr and redirect stderr as desired.)