chore: add MEMORY.md to gitignore#11
Conversation
- Exclude durable memory files from git - Prevents agent session state from being tracked - Aligns with pi-hard-no review scope (code review tool, not session data)
- Agent session state (MEMORY.md, .MEMORY.md) should not be code-reviewed - Skip auto-generated config files and dist directories - Clarifies review tool scope: code quality, not session data
royosherove
force-pushed
the
chore/memory-gitignore
branch
from
d4af3aa to
fec794e
Compare
![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 automated review suggestions for this pull request.
Reviewed commit: fec794e856
ℹ️ 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
- 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 address that feedback".
|
|
||
| - `MEMORY.md`, `.MEMORY.md` — agent durable session state (not code under review) | ||
| - Configuration files that are auto-generated or user-specific (e.g., `.env`, `.vscode/settings.json`) | ||
| - Lock files and dist directories (auto-generated, not code to review) |
There was a problem hiding this comment.
This new rule tells the reviewer to skip lock files entirely, which suppresses analysis of dependency-version changes and can miss supply-chain/security regressions in dependency-only updates. Because default-review-rules.md is used as the scaffold baseline for review-rules.md, projects that scaffold defaults will be instructed to ignore exactly the file type that often contains vulnerable component changes.
Useful? React with 👍 / 👎.
1 participant
Exclude durable memory files from git tracking.
All tests pass. Ready to merge.