Practise the standard verbs for caching effectively in GitHub Actions.
0 / 5 completed
1 / 5
Fill in: 'We ___ the dependency cache by a lockfile hash so a stale cache never serves outdated packages.'
We 'key' a cache — the standard, established CI collocation for tying a cache entry to a specific identifier. The other options aren't the recognised term here.
2 / 5
Fill in: 'A cache keyed too broadly can ___ a workflow into restoring dependencies that no longer match the lockfile.'
We say a bad cache key will 'trick' a workflow into using stale data — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ build outputs between jobs so a later job doesn't have to rebuild what an earlier one already produced.'
We 'share' outputs — the standard, simple collocation for passing artifacts between steps or jobs. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ cache hit rates over time to see whether our keying strategy is actually saving CI minutes.'
We 'track' a rate — the standard collocation for monitoring a metric over time. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ old, unused caches periodically since GitHub Actions enforces a total storage limit per repo.'
We 'prune' caches — the standard, established collocation for removing stale entries to free space. The other options aren't the recognised term here.