Repository navigation
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. |
Castiron custom codeEvaluated next: Trusted main policy: ✅ No new custom-code files detected. 48 mixed files remain; 0 existing customizations changed. Compared 48 existing customizations unchanged
8 more in the full report. A changed generated baseline means this report cannot reliably identify which handwritten lines changed. Inspect the custom-code diffDownload the exact patch produced by this run (requires repository access): gh run download 40400696164 --repo openai/openai-python \
--name castiron-custom-code-40400696164-1 --dir /tmp/castiron-custom-code-40400696164-1
git apply --stat /tmp/castiron-custom-code-40400696164-1/custom-code.patch
cat /tmp/castiron-custom-code-40400696164-1/custom-code.patchOr reproduce it from an SDK checkout containing the vendored reporter: git fetch --no-tags origin b421d9eac4176b0f753836839071b480b6c542c9 743ef5d001368dd8fed054f4a8d4c3078bc018e3
python3 scripts/castiron/custom_code_report.py report \
--base b421d9eac4176b0f753836839071b480b6c542c9 \
--head 743ef5d001368dd8fed054f4a8d4c3078bc018e3 --target-branch next --fetch --require-head-hash --public \
--out /tmp/castiron-custom-code-743ef5d00136
cat /tmp/castiron-custom-code-743ef5d00136/custom-code.patchThis is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR. |
Pin next's trusted Castiron checker to this repository's main commit
904ed3f6ba0f2351af67c9456e9f020401a8a7f8so next-targeted sync PRs can be evaluated. The current sync fails withmissing next pin allows only reviewed policy-only initialization.Only
.castiron-ratchet.jsonchanges. All existing budget/schema fields are unchanged. The pin selects the current main policy; it does not grant a larger effective budget or change generated ownership.Validation: exact one-file diff; existing JSON fields unchanged; pin points to authenticated main. Hosted checks and required review remain pending. The next branch must also have the merge queue required by the trusted checker before activation; no repository settings are changed by this PR.