Repository navigation
fix(ci): scope historical Eval synthetic fixture finding - #18
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
SonSangjoon
approved these changes
Sep 23, 2026
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 Eval rollout is blocked by a historical synthetic receipt-sanitization fixture that was previously documented as using no credential. Restore that single historical disposition in the central workflow, constrained to the exact Eval repository, commit, path, rule, line and full blob SHA-256.
The change creates a temporary history-only ignore file while retaining the existing trusted-base entries. Current-file and raw-blob scanning remain unchanged. No credential value is included, and no token authentication was attempted. The owner approved proceeding with this specific security PR; required CI and review still apply.
Validation:
The workflow matches the owner-reviewed patch. Rollback is a normal revert, which restores failure for this historical finding. This PR does not solve or authorize the separate initial-pin bootstrap transition, alter rulesets, bypass checks, or merge the Coffee Chat rollout PRs.