Repository navigation
Move review TSVs to LFS and guard large Git blobs - #51
Open
anotherjulien wants to merge 1 commit into
Open
anotherjulien wants to merge 1 commit into
anotherjulien wants to merge 1 commit into
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.
The review campaign left 55 TSV tables (243,541,953 payload bytes) in ordinary Git storage. This converts their current versions to Git LFS and prevents new oversized ordinary blobs without rewriting history or moving/deleting release tags.
All 55 paths, payload lengths and SHA-256 hashes match their original committed bytes at
d166b48884d396d61debc5aaa5a1822d27d41bc1. Large TSV deletion counts in the diff represent pointer conversion; the hydrated evidence tables are unchanged. The KB, source material, Device definitions and evidence-package subtrees are identical to main.Storage guard
Git storage policyCI job and document local use, hydration and required-check configuration. The guard reads Git objects without downloading LFS payloads.Historical ordinary blobs remain reachable. This is one normal descendant commit, not a storage purge. Existing release tags retain their exact object IDs.
Validation
Passed locally: 11 real-Git storage regression tests; original-byte/hash/length and staged-pointer comparisons for all 55 tables; Git LFS object/pointer integrity; all four evidence packages and 55 evidence acceptance tests; privacy across 21 generated artifacts and metadata surfaces; ESG and ECV with zero objective failures; the 807-artifact inventory; and the full exact-commit canonical-source, private-catalogue and Device gate. All 55 new LFS objects uploaded successfully. All six PR checks passed on the exact candidate. Completed logs confirm 222 KB unit tests, eight schema tests, 12 catalogue-status regressions, 11 storage tests, generated-output freshness and the complete deterministic integrity/claim/privacy gate, plus 55 evidence acceptance tests and the source/compliance checks. See full KB validation and compliance and storage validation. The PR remains open and mergeable; existing main and release-tag references were rechecked unchanged.
Candidate:
08ea0c7821dcfa083d8c6ad7c173e32d7b7189ab. No merge or new release is part of this task.