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

Don't display quick evaluation query runs in the history by default

Open
#2,783 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
developer-experience, tooling

Research direction

Start by locating the query history view and the quick evaluation flow in the VS Code extension. Decide whether quick evaluation runs should be hidden by default or not recorded, and make the chosen behavior available through the history menu if appropriate; done means regular runs remain visible while quick evaluation runs no longer bloat the default history.

Written by the indexing model from the issue text.

Description

enhancement VSCode

Is your feature request related to a problem? Please describe.

I use the query history regularly to go back to older query runs (both MRVA and local runs) and compare them to newer runs. However, when I develop or debug a query I often use the "quick evaluation" feature. This sometimes leads to a rather bloated history with lots of "quick evaluation" runs that are not interesting. (I have to delete them manually to get a cleaner history back)

Image

Describe the solution you'd like

One solution could be not display quick evaluation query runs in the history by default. E.g. they could be displayed via a menu point in the ... menu.

Describe alternatives you've considered

Another variant could be to just not record the history of quick evaluations (as an ephemeral-ness behaviour is somewhat implied in the name). Personally, I never needed to go back to the results of a quick evaluation.

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.