Conversation
…onoun detection; add tests
…; clarify Codex workflow
…I; tests: dry-run sanity
…sts: DRY-run check
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
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".
| home = /usr/bin | ||
| include-system-site-packages = false | ||
| version = 3.12.3 | ||
| executable = /usr/bin/python3.12 | ||
| command = /usr/bin/python3 -m venv /home/michael/soulfield/.venv |
There was a problem hiding this comment.
[P1] Stop committing local virtualenv artifacts
The change checks in an entire .venv tree (and the extracted GitHub CLI under tools/gh/), adding ~2 000 files and ~339 k lines of compiled/vendor code even though the commit message is a docs update. These files are environment-specific build outputs that belong in .gitignore; keeping them in Git bloats the repo, risks platform incompatibilities, and will drift every time dependencies are upgraded locally. It would be much safer to remove these directories from source control and rely on requirements.txt/installation scripts to recreate them.
Useful? React with 👍 / 👎.
|
Closing due to failing CI checks. Node and verify tests failing - needs investigation and rebase. |
1 participant
Title:
Summary
Checklist
Validation
1.
2.
Links