Repository navigation
Smarter disk cache: immutable completed GHA resources - #92
Open
stefanpenner wants to merge 1 commit into
Open
stefanpenner wants to merge 1 commit into
stefanpenner wants to merge 1 commit into
Conversation
Short 5m TTL forced revalidation of write-once Actions resources. Completed run/job JSON and job logs stay cache-fresh for 30 days (no network), cutting repeat-analysis cost. Bump cacheVersion to v5.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
User-facing speed item #3 (smarter cache for immutable data):
status: completedon body; logs path always immutable once fetchedcacheVersion→ v5 (invalidate old entries)Why
Re-running
oteon the same PR/commit re-hit GitHub for data that never changes after completion — rate budget + wall clock for no gain.Verify
go test ./pkg/githubapi/ -run 'Cache|Immutable|TTL|ETag|Auth'