AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

build: fix the custom linter cache wiring for CI

Public commit record

What the developer wrote

Authored by Olaoluwa Osuntokun

92/100 · Strong
build: fix the custom linter cache wiring for CI

In this commit, we fix two problems in the previous iteration of the
linter build cache.

The gha cache backend reads its credentials from the ACTIONS_RUNTIME_TOKEN
and ACTIONS_RESULTS_URL environment variables, but those are not exposed
to plain run: steps by default. We add the crazy-max/ghaction-github-runtime
step to expose them before the lint steps, otherwise the cache import or
export fails inside the manually invoked docker build.

The docker-container driver that setup-buildx-action installs doesn't
load the built image into the docker image store by default, but the lint
targets run the image with docker run. We add --load so the tagged
lnd-tools image is available to the lint steps.

We also only export the cache from the nightly run (LINT_WRITE_CACHE),
since PR-created caches aren't readable by other PRs and would only
churn the shared cache store. PR and merge queue runs still read the
cache that the nightly run exports.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit fixes the GitHub Actions CI setup for running a custom code linter. It makes sure Docker can read and write build caches correctly and that the built linter image is available for later steps. There is no user-facing security fix here; it is purely a build-infrastructure improvement.

Recommended action

No security action required. Treat as a normal CI maintenance commit.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.