verify-buildkit-cache
Verifying BuildKit Cache Effectiveness
Systematically verify—from CI logs only—that Docker RUN --mount=type=cache
(Go GOMODCACHE and GOCACHE) is:
- Persisted across jobs
- Restored by GitHub Actions
- Injected back into BuildKit
- Actually speeding up
go build
Prerequisites
This checklist assumes:
- Dockerfile uses BuildKit cache mounts:
RUN --mount=type=cache,target=/go/pkg/mod(GOMODCACHE)RUN --mount=type=cache,target=/root/.cache/go-build(GOCACHE)
- GitHub Actions workflow:
- Uses
actions/cache@v5to persist a host directory (CACHE_DIR, e.g.cache-mount/)
- Uses
More from hiromaily/go-crypto-wallet
shell-scripts
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
39makefile-update
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
34docs-update
Documentation update workflow. Use when modifying files in docs/ directory or any markdown files (*.md).
33btc-terminology
Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Use when working on BTC-related code, config files, or shell scripts.
33db-migration
Database schema and migration workflow. Use when modifying database schemas in tools/atlas/ or SQLC queries in tools/sqlc/.
30openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
25