docs: clarify collaborator-only pull request policy - #3948
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 code✅ No new custom-code files detected. 47 mixed files remain; 0 existing customizations changed. Compared 47 existing customizations unchanged
7 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 35887702627 --repo openai/openai-python \
--name castiron-custom-code-35887702627-1 --dir /tmp/castiron-custom-code-35887702627-1
git apply --stat /tmp/castiron-custom-code-35887702627-1/custom-code.patch
cat /tmp/castiron-custom-code-35887702627-1/custom-code.patchOr reproduce it from an SDK checkout containing the vendored reporter: git fetch --no-tags origin be9d66628ad7377bd36fe5a76ae6d735843f0e76 e75acdf3a4a7d2236f5e4f6a54d9d9d354d85c37
python3 scripts/castiron/custom_code_report.py report \
--base be9d66628ad7377bd36fe5a76ae6d735843f0e76 \
--head e75acdf3a4a7d2236f5e4f6a54d9d9d354d85c37 --fetch --require-head-hash --public \
--out /tmp/castiron-custom-code-e75acdf3a4a7
cat /tmp/castiron-custom-code-e75acdf3a4a7/custom-code.patchThis is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR. |
markstuart-oai
left a comment
There was a problem hiding this comment.
Reviewed e75acdf. The README and contribution guide consistently direct community contributions to issues, limit pull requests to collaborators, and preserve private security reporting and the existing development instructions. The PR template also removes the conflicting invitation to external pull requests. No actionable findings.
Validation: immutable documentation diff, link-target and repository-guidance inspection; exact-head hosted checks are successful or intentionally skipped. No tests or builds run locally.
Automated Release PR --- ## [3.19.1](openai/openai-python@v3.19.0...v3.19.1) (2026-09-23) ### Bug Fixes * **chat:** preserve single-pass tool iterables ([openai#3770](openai#3770)) ([33ffa1f](openai@33ffa1f)) * **client:** merge HTTP headers case-insensitively ([openai#3486](openai#3486)) ([5e39766](openai@5e39766)) ### Chores * **api:** clarify Chat Completions seed limits ([openai#3945](openai#3945)) ([be9d666](openai@be9d666)) ### Documentation * clarify collaborator-only pull request policy ([openai#3948](openai#3948)) ([ead1fa2](openai@ead1fa2)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: openai-sdks[bot] <284451331+openai-sdks[bot]@users.noreply.github.com>
Summary
Make the contribution guidance match the repository's collaborator-only pull request policy. The README links to CONTRIBUTING.md, both explicitly exclude PRs from non-collaborators, and community feedback goes through issues. Existing development instructions remain available to collaborators, and security reports continue through the private disclosure process.
Remove the conflicting invitation to external PRs from the pull request template.
Use absolute README links to the policy and security guide so package-page readers can follow them.
Test plan
git diff --checkand targeted policy/link checks pass.Documentation only; no SDK runtime, repository settings, or generated source changes.