syntaqxA repository's actions/cache entries can be listed, measured and deleted, in GitHub's shapes, so what the cache holds can be checked against its 10 GiB: GET /repos/{owner}/{repo}/actions/caches lists the entries saved (id, key, ref, version, size_in_bytes, created_at, last_accessed_at), narrowed by a key prefix and a ref, ordered by last use, saving or size in either direction, a page at a time; GET …/actions/cache/usage gives active_caches_size_in_bytes, active_caches_count and quota_bytes; DELETE …/actions/caches?key= deletes a key's entries (one ref's with ref) and answers with them, and DELETE …/actions/caches/{id} deletes one and answers 204. Listing needs the Read role and workflows:read, deleting the Write role and workflows:write; a deleted entry's objects go at once, or at the next sweep if the bucket refuses. The actions service answers caches, cache_usage and delete_caches; the workflow MCP tool has list_caches, cache_usage, delete_caches and delete_cache; and `g1t cache list|usage|delete` calls them (list pages past 100 up to --limit; delete takes an id or a key). The Actions guide says how to see and delete entries, and the OpenAPI document, the CLI reference and the MCP reference are regenerated.694d983History
- ..
- 0001_init.sql
- 0002_reusable_workflows.sql
- 0003_settings_access.sql
- 0004_self_hosted_runners.sql
- 0005_actions_cache.sql
- 0006_artifacts.sql
- 0007_run_protection.sql
- 0008_actions_access.sql
- 0009_run_attempts.sql
- 0010_jobs_self_hosted_lower.sql
- 0011_schedule_rules.sql
- 0012_runner_task_runs.sql
- 0013_action_registry.sql
- 0014_managed_workflows.sql
- 0015_runner_isolation.sql
- 0016_log_chunks.sql
- 0017_workspace_managed_workflows.sql
- 0018_desktop_runners.sql
- 0019_brokered_secrets.sql
- 0020_job_token_rotation.sql
- 0021_log_retention.sql
- 0022_runner_machine.sql