Conversation
…onoun detection; add tests
…; clarify Codex workflow
There was a problem hiding this comment.
Codex Review: Here are some suggestions.
Reply with @codex fix comments to fix any unresolved comments.
About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".
| # .-. .-. .-. . . .-. .-. .-. .-. | ||
| # |( |- |.| | | |- `-. | `-. | ||
| # ' ' `-' `-`.`-' `-' `-' ' `-' | ||
|
|
||
| __title__ = "requests" |
There was a problem hiding this comment.
[P1] Avoid committing virtualenv contents
This change checks in thousands of files under .venv/ (e.g. the vendored requests package) along with other generated artifacts like tools/gh/gh.tgz. These are machine‑specific dependency installs that should be rebuilt from requirements.txt rather than tracked. Keeping them in git bloats the repository by ~300k lines, causes constant diffs whenever the local environment changes, and risks shipping outdated binaries. Please drop the .venv directory and other build outputs from version control and rely on dependency manifests instead.
Useful? React with 👍 / 👎.
Title:
Summary
Checklist
Validation
1.
2.
Links