Document static reachability analysis behavior for excluded paths
What does this MR do and why?
Documents the expected behavior of static reachability analysis when dependencies are located in excluded directories.
We mark those packages as not_found
to respect user intent and reduce FPs. It also improves scan efficiency by not analyzing non-prod code paths.
Related to DS: Fix java reachability E2E tests (#577752) • Orin Naaman • 18.6
Screenshots or screen recordings
Before | After |
---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.