Repository navigation
chore: ignore Python bytecode artifacts - #15
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe ChangesPython cache ignore rules
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Merge Risk: ⚪ Minimal · up to The change only adds appropriate ignore patterns for retired Python cache and bytecode artifacts. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary\n\n- Ignore Python cache directories and bytecode artifacts left by the retired Python implementation.\n- Prevent local migration-era cache files from appearing as untracked worktree changes.\n\n## Validation\n\n- git diff --check\n- git check-ignore -v bin/pycache/wtcpython-311.pyc tests/pycache/test_commands.cpython-311-pytest-9.0.3.pyc\n\nNo runtime code changes.
Summary by CodeRabbit