Repository navigation
explain the map shown for very large graphs - #245
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
![graphify-labs-staging[bot]](https://avatars.githubusercontent.com/in/4517131?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found by static checks — no coupling regressions or blocking issues in the code graph. That is not the same as safe to merge: see what was not checked.
Not checked: tests were not run; no formal proof of the changed code.
Graphify review — findings
Adds a “Very large repositories” section that surfaces a precomputed structural map with node/edge totals when the browser cannot lay out every node, while MCP and Ask continue to query the full graph. Pre-October 2026 builds fall back to a re-index prompt instead. The troubleshooting table now lists the two new banners and their recovery steps.
No blocking issues surfaced. 1 lower-confidence candidate did not survive cross-model review.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 14 functions depend on the 14 functions this change touches.
Health — grade A; no new coupling hotspots.
Verification — 14 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 14 function(s) in the blast radius were not formally verified this run
Very large repositories used to fail on the graph page with "This graph is too large to display". Now the page shows a precomputed map of the graph's structure, with the notice "This graph is too large to draw node by node". MCP and Ask still answer from the full graph.
This adds a short section to the graphs page explaining what the map is. Some builds, including any made before October 27, can't be shown as a map and still show the older message. The section tells you to index again in that case. It also adds both messages to the troubleshooting table.