Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support for query suites

Open
#615 5 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode, yaml
Domain
tooling

Research direction

Read the linked CodeQL query-suite documentation, then inspect the existing YAML mode, folder-based query execution, and query history entry points. Done means *.qls files support their schema for authoring and can be selected to run against the current database while appearing in query history, including a discoverable path for well-known suites.

Written by the indexing model from the issue text.

Description

enhancement VSCode

Is your feature request related to a problem? Please describe.
It'd be great to have the extension understend CodeQL query suites. This would ideally cover both authoring them and executing query suites on the currently-selected database.

Describe the solution you'd like
The *.qls format is effectively YAML with a particular schema, so switching to YAML mode at least gives syntax highlighting at the moment. Having the schema used automatically for auto-complete suggestions and error checking would be great, though.

For bulk query execution, selecting a *.qls file would be more flexible than the current "run all queries in this folder" approach. There's a slight UI challenge around how to make well-known query suites discoverable.

Describe alternatives you've considered
The current workaround is to edit *.qls files after manually selecting YAML mode, and to use the CodeQL CLI to run query suites, though that doesn't insert them into the query history view.

Dominant language
TypeScript
Stars
539
Forks
240
Avg merge
2d 6h
Merged PRs (30d)
29

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/vscode-codeql

All issues in github/vscode-codeql

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.