Organize reproduction steps, expected behavior, and the current contribution policy
Suggested learning time: 45 minutes.
- 1Current contribution policy
- 2Reproduction and evidence
- 3Small reviewable draft
- 4Authorized posting decision
Original learning map: arrows show the reading or decision sequence, not a measured execution trace.
Prerequisite chapter
Use a debugger to test one hypothesis
Status of this chapter
This textbook was authored from reading sources. No actual repository builds, tests, debugging, API calls, or issue/PR posts were performed. Practical work below is an exercise to undertake; reading is not an execution result.
Learning objectives
- Organize reproduction steps, expected behavior, and the current contribution policy
Contributions beyond pull requests
Codex's current official policy does not accept external code contributions or pull requests. It accepts bug reports, reproductions, root-cause analyses, and feature requests. Do not make submitting a pull request the only path through the Codex course. Even if you learn by making a local fix, your deliverable can be a draft analysis.
Follow each repository's process
The Python SDK is a public mirror whose external pull requests are incorporated internally. MLflow recommends discussing the approach in an issue first. Recheck each repository's requirements for signatures, the DCO, a CLA, and AI use. A sign-off affirms your rights to contribute; do not add one as a mere formality.
Keep the task small
For a real issue, check whether it is open, who is assigned, related pull requests, and recent maintainer comments. Do not assume that labels alone mean it is suitable for beginners or that no one has started work. Clearly label fictional exercises as exercises and do not post them. Narrow your contribution to something such as adding reproduction details, addressing one boundary condition, or making an ambiguous explanation concrete.
Practical exercise: Practice designing the smallest useful contribution
- Read the current contribution and AI-use policies.
- For a real issue, check related pull requests, the assignee, and the latest comments.
- Record expected behavior, actual behavior, reproduction steps, the environment, evidence, and unknowns.
- Create an issue draft or a local diff. Do not post it.
Deliverable: A draft that can be reviewed before it is posted
Understanding checks
Answer in your own words before reading the answers. The answers and explanations below are for self-review, not automatic scores or execution results.
Can submitting a pull request be the completion criterion for the Codex course?
Answer: That is not appropriate under the current policy. Make reproduction and analysis the goal, and consider a pull request in a different repository whose contribution policy permits it.
Your learning progress
Recording mode: manual.
- Not started
- Read
- Tried
- Can explain
Do not mark an exercise as practiced merely because you viewed it.
Material used in this chapter
openai/codex contribution and development guide, databricks/databricks-sdk-py contribution and development guide, mlflow/mlflow contribution and development guide, unitycatalog/unitycatalog contribution and development guide
Return to repository entry points · Offline experiment worksheet
MENTAL MODEL / REASONING ORDER
From an announcement to your own decision.
Compare the announcement with the conditions in the paper and official documentation.
Sources
Publication dates belong to the source; access dates record when it was checked. Community observations are separate from official statements.