skills.rest
mizchi
mizchiCOMMUNITY
Explore all skills by this author →
Website𝕏@mizchiGitHub

flaker-storage-cache-on-ci

Cache flaker's DuckDB storage across GitHub Actions runs using actions/cache.

320|3|Updated Apr 24, 2026
Search Tags:#workflow#cache#github-actions#duckdb#ci#flaker
One-click install
npx skills add https://github.com/mizchi/skills --skill flaker-storage-cache-on-ci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flaker-storage-cache-on-ci
Source: https://github.com/mizchi/skills/tree/main/devops/flaker-storage-cache-on-ci
Command: npx skills add https://github.com/mizchi/skills --skill flaker-storage-cache-on-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist flaker's DuckDB storage across GitHub Actions runs to preserve history and enable cross-run ingestion. The default DuckDB file location is declared via flaker.toml and must persist between runs to maintain KPI and quarantine results. This Skill provides a repeatable workflow pattern that encodes the cache key shape, fetch-depth requirements, and import-step placement used by internal flaker users.

Core Features & Use Cases

  • Cache flaker data between CI runs using actions/cache@v4 with a path matching flaker.toml storage path.
  • Support multi-source ingestion (vitest reports, custom adapters) by restoring and updating flaker history across runs.
  • Guidance for debugging history loss when using flaker apply or flaker run with --gate options.

Quick Start

Configure your GitHub Action workflow to cache the .flaker/data file (or the path defined by flaker.toml [storage] path) and ensure fetch-depth is sufficient to derive changes across runs.

Frequently Asked Questions about flaker-storage-cache-on-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist DuckDB storage data across GitHub Actions runs?▼

Persist DuckDB storage across GitHub Actions runs by configuring actions/cache@v4 to cache the .flaker/data file, matching the path declared in flaker.toml [storage] to maintain history between runs.

Why does flaker lose history when using cache on CI workflows?▼

Flaker history loss on CI typically occurs when the actions/cache path does not align with the flaker.toml [storage] path, or when git fetch-depth is insufficient to derive changes across runs.

Can I use vitest reports for cross-run ingestion in CI caches?▼

Yes, you can feed vitest reports into flaker during CI workflows by restoring the cached DuckDB history first, allowing multi-source ingestion to update and preserve results across runs.

Do I need a specific git fetch-depth for flaker data caching in GitHub Actions?▼

Yes, you must configure a sufficient git fetch-depth in your GitHub Actions workflow to properly derive changes across runs when restoring and updating cached flaker history.

How to debug flaker history loss with apply or run --gate options on CI?▼

Debug flaker history loss by verifying that your CI cache key shape, consistent import-step placement, and storage path alignment are correctly configured before executing apply or run --gate options.

Related Skills

Explore More Software Engineering Skills→
math-incmath-inc
1.2k

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

Official
Intermediate
WindXRanWindXRan

test-flakiness

Analyze CI logs and JUnit XML to detect flaky tests and recommend quarantine actions.

Community
Advanced
Haseeb-ArshadHaseeb-Arshad
2

tdd-guide

Generate tests and analyze coverage for Jest, Pytest, JUnit, and Vitest.

Community
Advanced
spencerbeggsspencerbeggs
2

actions-cache-and-artifacts

Manage GitHub Actions dependency caching, artifacts, and toolchain installation.

Community
Advanced