Repository navigation
chore(organisation): own the two ingestion tests under source-intake, not app-experience's document-* glob - #3621
Conversation
… not app-experience's document-* glob tests/document-extraction-source-fidelity.test.ts exercises src/lib/extractors/** and worker/behavior.ts, and tests/document-detail-demo-window.test.ts exercises src/lib/document-detail.ts; source-intake owns all of those. Explicit source-intake entries now take them from app-experience's tests/document-* glob. The other 45 glob-owned search-/document- tests exercise app-experience UI or client code and stay put. Adds a real-manifest ownership regression test.
There was a problem hiding this comment.
BigSimmo has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYour organization has reached its usage spending cap. Adjust your spending cap in the billing tab. Next included review available in 7 minutes. View limit details
Comment |
|
Claude encountered an error after 2s —— View job I'll analyze this and get back to you. |
PR Summary by QodoAssign two ingestion tests to source-intake
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
Code Review ✅ Approved🟢 Low risk · The manifest adds explicit test ownership entries and a regression assertion; these affect repository organization only, leaving runtime behavior unchanged. Moves the VerificationRules No rules evaluated Functional validation Not enabledAuto-approval Approved For more verification details, comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Important Your trial ends in 4 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can see how risky a PR is at a glance with blast radius labels |
Qodo FixerNo findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR. |
CodeAnt PR Risk: Low Risk
Assessed commit: |
User description
Summary
tests/document-*glob had claimed now belong tosource-intake, the system that owns the code they test:tests/document-extraction-source-fidelity.test.tsexercisessrc/lib/extractors/**andworker/behavior.ts.tests/document-detail-demo-window.test.tsexercisessrc/lib/document-detail.ts.source-intake.jsonentries take precedence over the glob, so app-experience'stests/search-*andtests/document-*globs stay as they are. No ownership check, gate or budget changed.tests/search-*/tests/document-*tests, 26 already had explicit owners elsewhere. The other 45 that the globs still own test app-experience UI or client code (document viewer, search results, pins, shell, routing) and stay put. Nosearch-*test exercises answer-engine code, so none moved there.tests/maintain-docs-system.test.tsthat checks the real manifests: the two tests resolve tosource-intake, and viewer and search UI tests stay withapp-experience.Areas touched: Knowledge and records
Verification
vitest run tests/maintain-docs-system.test.ts tests/organisation-*.test.ts: 423 passed;npm run verify:pr-localpassed every step up totypecheck. The shared box ran out of memory there (exit 137), so I re-rannpm run typecheckon its own, which passed (recorded a pass for "typecheck:internal"). Its remaining full unitteststep was left to CI.Risk and rollout
Notes
tests/document-ingress-safety.test.tscovers ingestion-safety logic, but its subjectsrc/lib/document-ingress-safety.tsis explicitly owned bydelivery. Moving only the test would split it from its code, so both should move together if that is wanted.Summary by cubic
Moves ownership of two ingestion tests from
app-experience's broadtests/document-*glob tosource-intake, which owns the code they exercise.tests/document-extraction-source-fidelity.test.tsandtests/document-detail-demo-window.test.tsnow have explicit entries insource-intake.json, which take precedence over the glob and leave the other 45 glob-owned UI and client tests withapp-experience.tests/maintain-docs-system.test.tsasserting the real manifests resolve these tests tosource-intakeand viewer/search UI tests stay withapp-experience.Written for commit 0c72c05. Summary will update on new commits.
CodeAnt-AI Description
Assign ingestion tests to source-intake
What Changed
source-intake, which owns the code they test.app-experience.Impact
✅ Ingestion tests counted under source-intake✅ Viewer and search tests remain with app-experience✅ Test ownership changes are checked against the manifests💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.