Repair feed pipeline integrity and validation#5
Merged
Conversation
Contributor
Feed registry validation report |
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.
Why this repair is needed
The hourly Space & Defense workflow filtered
feeds.yamlto two areas and then ran the full builder. That periodically rewroteindex.htmlandfeeds/all.*as a space-only snapshot. Other writer workflows also lacked a shared lock and could collide during Git pushes.What this PR changes
feeds.yaml, XML, JSON, andindex.htmlcompletenessSafety
repair/feed-pipeline-integrityVerification before merge
CI must compile the scripts, validate all 2,327 lines of the registry, parse every committed XML/JSON output, and confirm every configured area appears in the public directory.