GitHub search tool returns zero matching GitHub Issues despite there being many

Abierto
#8,930 0 comentarios 1 reacción 2 asignados Ver en GitHub

@alexr00 ya está trabajando en esto.

Desde el 5/9/2026.

  • #8938 de @copilot-swe-agent — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

bug
Problem

The github-pull-request_doSearch language-model tool returns zero results when searching a repository that is not the active workspace repository, even when actually such results do exist.

Specific example:

  • Repository parameter: microsoft/vscode
  • Query: is:issue is:open assignee:jruales
  • Actual result: totalIssues: 0
  • Known matching issue: https://github.com/microsoft/vscode/issues/332663 is open and currently assigned to jruales. The issue_fetch tool also returns that assignee correctly.

Equivalent queries such as is:issue assignee:jruales, assignee:jruales, and is:issue is:open involves:jruales also return zero.

The tool itself includes an Open on GitHub.com link. Opening that link shows the expected assigned issues, while the tool's structured result for the same query reports zero.

Image
Expected

The explicit repo parameter should scope the search independently of whichever repository is open in the workspace. Alternatively, if the requested repository cannot be searched, the tool should return an explicit error explaining why rather than a successful-looking empty result.

Likely cause

SearchTool resolves or creates the requested repository, but then calls FolderRepositoryManager.getIssues(). Its paging path filters repositories against active workspace remotes, which may exclude the synthetic repository created for the explicit repo parameter. The tool then returns a successful-looking empty result.

Lenguaje dominante
TypeScript
Estrellas
2.6k
Forks
796
Merge medio
16 h 26 min
PR fusionados (30 d)
44

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/vscode-pull-request-github

Todos los issues de microsoft/vscode-pull-request-github

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.