data(brand): backfill verified flag on bulk-seeded brands - #44
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
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
Backfill the
verifiedfield on the 129 brand records that were missing it (bulk/auto-seeded brands), settingverified: falseto match the bulk-import policy. All 189 brands now carry the field, closing the "brand category missing verified metadata" gap tracked in #1.Changes
data/brand/**/*.jsonrecords getverified: false(inserted beforesource_urls, matching the 60 brands that already had the flag).verified, sosite/public/v1is byte-identical (no dump refresh needed).Verification
python -m app.validatePASSpython TechEngine/integrity_check.py data --strictPASSgit diff --check origin/main...HEADPASSsite/orsite/publicchanges → site build N/ACloses #1