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

Restore-only dependency caching for managed Code Quality pull requests

Abierto
  • ¿Algo no está bien?
#4,228 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, go, typescript
Área
ci-cd, devtools

Línea de trabajo

Start by reading the managed Code Quality workflow generation and the dependency-caching implementation in this repository; the issue identifies the dynamic/github-code-quality/codeql job and the Go module cache at ~/go/pkg/mod. Compare the managed configuration with the documented setup API and existing restore-only cache modes. Done means a supported policy can restore dependencies on managed PR analysis while limiting cache writes to the default branch, with analysis and upload preserved.

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

Descripción

Managed Code Quality Go analysis can save a multi-gigabyte, PR-scoped module cache that competes with other required CI caches. Is there a supported way to retain dependency restores while limiting managed Code Quality cache writes to the default branch?

In this public Go job, the generated workflow used github/codeql-action@v4 resolved to 24c54180a607b1449ed407dd24f251e4e9147c8d, with dependency-caching: true. It packaged 9,980,805,362 uncompressed bytes and saved a 5,365,575,023-byte dependency archive under refs/pull/7708/head. The exact action source caches ~/go/pkg/mod for Go; this archive is not GOCACHE. Other completed attempts spent time packaging the same final key before cache reservation failed.

Owned Advanced CodeQL supports dependency-caching: restore, and owned workflows support cache-mode: read. Neither declaration governs the separate dynamic/github-code-quality/codeql job. The documented Code Quality setup API exposes no equivalent cache control. Code Quality is configured independently of code-scanning default setup in this repository.

A supported restore-only policy for managed PR analysis, with an appropriate default-branch cache writer, would avoid these redundant copies while preserving analysis and upload. We have separately reduced duplicate module/build-cache writers in repository-owned CI; that does not configure the managed producer.

If this control already exists, please point us to its supported configuration. Otherwise, please consider exposing a managed dependency-cache mode or equivalent scoped cache access. The relevant local outcome is tracked in devantler-tech/ksail#7348.

Lenguaje dominante
TypeScript
Estrellas
1.7k
Forks
498
Merge medio
1 d 17 h
PR fusionados (30 d)
56

Preparar el entorno

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 github/codeql-action

Todos los issues de github/codeql-action

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.