Commit be94afd
authored
feat(checks-rs): plumb kache_github_cache input to kache-action (#113)
kache-action falls back to GitHub Actions cache when no S3 remote is
configured (github-cache defaults true). On persistent self-hosted
runners the on-disk kache store already survives between runs, so the
multi-GB save/restore round-trips to the GH cache backend are pure
overhead (observed: a 10+ minute 'Post Setup kache' upload after a cold
build). New boolean input kache_github_cache (default true — no behavior
change for existing callers) passed to both kache-action invocations;
self-hosted callers set it false for a purely local store.1 parent 11e886d commit be94afd
1 file changed
Lines changed: 7 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
163 | 163 | | |
164 | 164 | | |
165 | 165 | | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
166 | 170 | | |
167 | 171 | | |
168 | 172 | | |
| |||
351 | 355 | | |
352 | 356 | | |
353 | 357 | | |
| 358 | + | |
354 | 359 | | |
355 | 360 | | |
356 | 361 | | |
357 | 362 | | |
| 363 | + | |
| 364 | + | |
358 | 365 | | |
359 | 366 | | |
360 | 367 | | |
| |||
0 commit comments