Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Restore-only dependency caching for managed Code Quality pull requests

Offen
  • Stimmt etwas nicht?
#4,228 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, go, typescript
Bereich
ci-cd, devtools

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
1.7k
Forks
498
Ø Merge
1 T. 17 Std.
Gemergte PRs (30 T.)
56

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/codeql-action

Alle Issues in github/codeql-action

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.