Repository navigation
Move review TSVs to LFS and guard large Git blobs - #51
Merged
Merged
Conversation
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
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.
Move all 65 review TSV tables (243,550,626 payload bytes) to Git LFS and prevent new oversized ordinary Git blobs. The updated branch includes current
mainat7102cffdcee8f3fd0f66aaca956472143508133f, including the ten WHO 25 oracle fixtures added by PR #49.All 65 paths, payload lengths and SHA-256 hashes match their original bytes on that main commit. The large deletion counts represent pointer conversion; hydrated table contents are unchanged. All other repository content matches main except the six storage-policy/configuration files. The entire KB, source material, Device definitions and evidence packages are unchanged.
Storage guard
Git storage policyCI job and document local checking, hydration and required-check configuration. The guard reads Git objects without downloading LFS payloads.Historical blobs remain reachable. No history, main branch or release tag is rewritten, and no release is created.
Validation
Fresh exact-commit canonical-source, private catalogue, Device completeness and catalogue regressions passed. The success status was published and verified on GitHub for this candidate. Hosted CI results for the refreshed branch are pending; the earlier 16 October results apply only to the original commit.
Validated candidate:
96cdd15c1a1e1f3a89cf6a1a5b7929b3b3bef0ae. Merged into main as88d61b3f3bf1456a708b62b0e3de6ed2242960eeon 2026-10-22. Storage, mechanical and catalogue checks had passed; broader KB/privacy CI was still running at merge time. Fresh catalogue validation was also published and verified for the main merge commit.