Skip to main content
The GitHub CI resource mounts GitHub Actions workflows and runs as a read-only virtual filesystem. For token setup, see GitHub CI Setup.

Config

Filesystem Layout

Example:

Workflows

/ci/workflows/ lists all workflows defined in the repository. Each .json file contains the workflow metadata (name, path, state).

Runs

/ci/runs/ lists recent workflow runs within the configured time window (default 30 days). The created API parameter filters server-side. Each run directory contains:
  • run.json - run metadata (status, conclusion, event, branch, actor, timing)
  • jobs/ - one .json and .log pair per job
  • annotations.jsonl - check annotations (warnings, errors) across all jobs
  • artifacts/ - downloadable build artifacts

Jobs

Each job has two files:
  • <job-name>_<job-id>.json - job metadata with steps and timing
  • <job-name>_<job-id>.log - full job log (plain text)

Artifacts

Artifacts are served as .zip files matching the GitHub API download format.

Cache

The GitHub CI resource uses IndexCacheStore with remote_time-based fingerprinting. Completed runs and jobs are effectively immutable and benefit from long cache TTL.

Example

Shell Commands

Standard commands available on the mounted GitHub CI tree:

Working with CI Data