Split GitHub cache and harden rate limiting#54
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
diffkit | 6165847 | Commit Preview URL Branch Preview URL |
Apr 10 2026, 07:52 PM |
stylessh
added a commit
that referenced
this pull request
Apr 18, 2026
* Split GitHub cache and harden rate limits * Document GitHub cache architecture
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.
This switches key GitHub-backed reads to a split cache model with D1 namespace/version state and KV-backed payload storage, including the migration and Wrangler binding for GITHUB_CACHE_KV. It expands split-cache coverage across viewer, repo lists, pull and issue detail/activity data, and repo metadata like collaborators, teams, and labels, while webhook and mutation paths now bump namespace versions for invalidation. It also hardens GitHub API usage by adding stale-if-rate-limited cache behavior, adaptive freshness under low quota, and an Octokit throttle/retry policy that retries safe reads but avoids replaying writes. On the client side, it preserves the latest render-performance work from main while removing the 15s PR status polling loop so status refreshes rely on focus and the newer component boundaries instead of a constant interval.