Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

githubIssues.queries is applied to auto-detected linked worktrees

Abierto
  • ¿Algo no está bien?
#9,141 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, typescript, vscode
Área
developer-experience

Línea de trabajo

Start in the issue state manager where githubIssues.queries is read, and check the extension manifest for its resource scope. Trace how the query list is reused across detected repositories and how an empty list falls back to the default. Done means each worktree gets its own configured queries, including an explicit empty list.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

  • Extension version: 0.172.0
  • VSCode Version: Not recorded
  • OS: macOS (version not recorded)
  • Repository Clone Configuration (single repository/fork of an upstream repository): One main worktree with linked worktrees for the same repository
  • GitHub Product (GitHub.com/GitHub Enterprise version x.x.x): Not recorded

Steps to Reproduce:

  1. Open the main worktree in VS Code.
  2. Keep "git.detectWorktrees": true so linked worktrees are detected and shown in Source Control.
  3. Configure a custom githubIssues.queries value for the main worktree.
  4. Open the GitHub Issues view and refresh it.

Actual:

The configured query categories are also applied to the auto-detected linked worktrees. I cannot configure the queries for the main worktree without also applying them to those linked worktrees.

Setting githubIssues.queries to an empty array does not disable the queries; the extension replaces the empty array with its default query.

Expected:

githubIssues.queries should be resolved per repository/worktree, so the main worktree can use its configured queries while linked worktrees can use their own configuration or no query categories. An explicit empty array should remain empty.

This should work while "git.detectWorktrees": true remains enabled, since I want the linked worktrees to continue appearing in Source Control.

Additional context:

The extension manifest declares githubIssues.queries as a resource-scoped setting, but the issue state manager appears to read it without a resource and reuse the resulting query list for all detected repositories. It also replaces an empty query list with the default query.

Lenguaje dominante
TypeScript
Estrellas
2.6k
Forks
807
Merge medio
1 d 21 h
PR fusionados (30 d)
70

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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.