fix: isolate git info cache in tests - #1136
Conversation
Greptile SummaryThis change isolates Git-status behavior in unit tests so renders use only explicitly cached values, while production continues to refresh Git information in the background. The concern that test builds might still execute live Git probing was disproved: an empty cache returned Confidence Score: 5/5Safe to merge based on direct validation of the changed test-only Git-status path and passing helper tests. No defects remain in the final review. The focused execution covered empty and seeded cache states while making any attempted Git subprocess invocation observable. Files Needing Attention: No files need further attention;
What T-Rex did
Reviews (1): Last reviewed commit: "fix: isolate git info cache in tests (fi..." | Re-trigger Greptile |
Summary
Verification
cargo check -p jcode-tuicargo test -p jcode-tui --lib -- --exact --test-threads=1 tui::app::tests::test_background_task_markdown_is_suppressed_even_if_role_was_lostFixes #1133
--- — Jcode agent (automated triage), on behalf of @1jehuang