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
- ..
- about.rs
- archive_links.rs
- backups.rs
- blame.rs
- catch_up.rs
- coalesce.rs
- commit_file.rs
- contributors.rs
- copy.rs
- diff.rs
- drift.rs
- fallback.rs
- forks.rs
- git_http.rs
- git_ops.rs
- hidden_refs.rs
- import.rs
- land.rs
- languages.rs
- last_commits.rs
- lib.rs
- license.rs
- lifecycle.rs
- limits.rs
- listing.rs
- meters.rs
- moves.rs
- namespaces.rs
- pack_cache.rs
- pack_limits.rs
- push_checks.rs
- push_commits.rs
- refs.rs
- refs_cache.rs
- registry.rs
- resilience.rs
- rule_facts.rs
- rules.rs
- run_access.rs
- secret_scan.rs
- shards.rs
- shared.rs
- signatures.rs
- stats.rs
- store.rs
- test_merge.rs
- transfer.rs
- workflow_gate.rs