Microsoft/vscode

Update GitHub Issue Notebooks due to GitHub issue query breaking change

Open

#252,667 opened on Jun 27, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)TypeScript (74,848 stars) (10,221 forks)batch import
engineeringhelp wanted

Description

Talked about here: https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/#mag-api-support-for-issues-advanced-search

You can see the difference in behavior if you open this GitHub issue query vs running this GitHub Issue Notebook cell.

GitHub Issue Notebooks loads results:

Image

GitHub Issues does not:

Image

From @RileyBroughten

You'll need to use OR between the repo filters, spaces are treated as AND operators with the introduction of boolean operators.

So we'll need to update all of our Notebooks before September 4 otherwise they will be broken...

But this is trickier because from within the notebooks I don't think we have a way to tack on this query parameter to adopt this before Sept 4th... so either we need a feature of GHIN that lets you provide this, or we just make the change after they're all broken.

Contributor guide

Tech stack
typescript
Domain
toolingdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with GitHub Issue NotebooksBasic knowledge of GitHub API query syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Read the GitHub changelog post about boolean operators (https://github.blog/changelog/2025-03-06 github issues projects api support for issues advanced search and more/). Understand the change from space separated repo filters requiring OR. Search the vscode repository for existing GitHub Issue Notebook files (likely .github issues extension) and identify all occurrences where multiple repo: filters are used. Replace spaces with OR operators between repo: queries. Test the updated notebooks to ensure they return the same results as the GitHub Issues web interface. Consider adding a feature to the GHIN to support the new query syntax before the deadline if needed.