Refactor: Reorganize repository structure#181
Conversation
… to designated folders
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
Reviewer's GuideRefactors the repo layout by moving shell/Python scripts under scripts/, consolidating memory MCP tests under router/tests, relocating root tests into tests/, and updating imports, docs, and CI workflows to match the new structure. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- Several tests now manipulate sys.path manually to reach router and scripts modules; consider turning router and scripts into proper packages or using relative imports to avoid ad‑hoc path injection and make imports more robust.
- The long sys.path parent traversals (e.g., in scripts/verification/verify_breaker.py) are a bit brittle; encapsulating this in a helper or using a consistent project root discovery mechanism would reduce duplication and future breakage if the layout changes again.
- Since start-stack.sh now calls scripts/sync_gemini_token.py, it might be worth adding a simple check that the script exists or fails fast with a clear message if the repository structure is not as expected.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Several tests now manipulate sys.path manually to reach router and scripts modules; consider turning router and scripts into proper packages or using relative imports to avoid ad‑hoc path injection and make imports more robust.
- The long sys.path parent traversals (e.g., in scripts/verification/verify_breaker.py) are a bit brittle; encapsulating this in a helper or using a consistent project root discovery mechanism would reduce duplication and future breakage if the layout changes again.
- Since start-stack.sh now calls scripts/sync_gemini_token.py, it might be worth adding a simple check that the script exists or fails fast with a clear message if the repository structure is not as expected.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
|
Warning Review limit reached
Next review available in: 39 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (32)
✨ 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 |
This PR reorganizes the repository structure by moving scripts to
scripts/and python tests totests/, merging the duplicate memory MCP tests intorouter/tests/test_memory_mcp.py, and updating all references, CI workflows, and documentation accordingly.Summary by Sourcery
Reorganize test and script layout into dedicated scripts/ and tests/ directories and merge duplicate memory MCP tests into a single router-focused suite.
Bug Fixes:
Enhancements: