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

CI: packaging workflow misses most extension workspaces; yarn lint never runs

Abierto
  • ¿Algo no está bien?
#1,143 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
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, typescript
Área
build-system, ci-cd, testing-qa

Línea de trabajo

Read .github/workflows/build.yaml and test-positron.yaml, then compare test.yaml and the workspace dependencies described in the issue. Verify which extension workspaces and root manifests need coverage, and run yarn lint to assess the current backlog. Done means packaging and Positron checks trigger for relevant changes and lint is run in CI with the agreed blocking behavior.

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

Descripción

Problem

Two CI coverage gaps:

1. build.yaml path filter is too narrow

.github/workflows/build.yaml ("Build VS Code Extension", which runs vsce package) only triggers on:

paths:
  - 'apps/lsp/**'
  - 'apps/vscode/**'

The packaged extension also bundles apps/vscode-editor, apps/vscode-markdownit, apps/quarto-utils, and most of packages/* (core, editor-*, quarto-core, _-prefixed packages, build, tsconfig, eslint configs). It also depends on root package.json, yarn.lock and turbo.json. A PR that touches only those files doesn't get a packaging check. test-positron.yaml has the same problem (it only triggers on apps/vscode/**).

test.yaml has no path filter, so tests do run. The gap is specifically that packaging and Positron tests don't run.

Fix: widen paths to cover every workspace in the extension's dependency closure plus the root manifests, or drop the path filter.

2. yarn lint never runs in CI

No workflow runs yarn lint, so lint errors build up unnoticed. Running it today will probably surface a backlog. Either fix those first, or add the job as non-blocking at first.

Fix: add a lint job to test.yaml (after yarn install). Consider doing this together with, or right after, the ESLint 10 flat-config migration (deps-upgrade-eslint-prettier.md), so we don't fix lint errors under a config that's about to be replaced.

Related

The yarn install --immutable --immutable-cache --check-cache flags used in these workflows are Yarn 2+ only, and Yarn 1 ignores them, so CI doesn't enforce the lockfile. That's tracked as the first step of the dependency-upgrade plan and should be fixed alongside this.

Found during the dependency-upgrade research.

Lenguaje dominante
TypeScript
Estrellas
655
Forks
64
Merge medio
22 h 16 min
PR fusionados (30 d)
42

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 quarto-dev/quarto

Todos los issues de quarto-dev/quarto

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.