Repository navigation
perf: freeze daily history and reduce database churn - #168
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Save completed GitHub and token days instead of repeatedly rebuilding and transferring history. Today’s work remains mutable; PR cards show cumulative totals, with past cards and links preserved.
Consolidate current PR evidence, push commit lists, and accepted summaries into their existing parent tables. One automatic migration preserves existing data and removes three redundant tables, leaving 23 application tables versus 24 originally. Older readers/workers may fail briefly until the new deployment is active.
Validation: 288 passing tests; lint, both Knip modes, and type-checking pass. The implementation was also checked with a local PostgreSQL migration and historical replay preserving 465 displayed items and 4,924 token days. Production build passed with GitHub embed 403 warnings.