Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Restore-only dependency caching for managed Code Quality pull requests

Ouverte
  • Quelque chose ne va pas ?
#4,228 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github-actions, go, typescript
Domaine
ci-cd, devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
1.7k
Forks
498
Merge moyen
1 j 17 h
PR mergées (30 j)
56

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/codeql-action

Toutes les issues de github/codeql-action

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.