sanitize(fixture): scrub real-case filename from valid-evidence-artifact example#23
Merged
Conversation
…act example examples/valid-evidence-artifact.json carried the real-case original_filename "console faults.rtf" (pre-existing on main, not from PR #20). Everything else in the fixture is already synthetic. Forward-scrub to a synthetic filename. NOTE: this file was already public on main, so the value persists in git history — a history rewrite (filter-repo/BFG) is the complete fix and is a separate deliberate op (rewrites public history; affects anyone who cloned).
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.
Removes the last real-case data string on
main:examples/valid-evidence-artifact.jsoncarriedoriginal_filename: "console faults.rtf"(pre-existing, not from #20). Everything else in the fixture is already synthetic. Forward-scrubbed tosynthetic-console-log.rtf.History note: the value was already public on
main, so it persists in git history. A full scrub needs a history rewrite (git-filter-repo/BFG) — a separate deliberate op since it rewrites public history and forces re-clones. Flagging for your decision.