Skip to main content
Use this when you know a name in the repository and want the code around it. Run the commands from the repository root after a map exists in graphify-out/, and replace YourService and YourRepository with names from your graph.

​
Who calls this

--context call keeps call relationships. explain prints one concept, its source, and its connections. In the small example project, asking what calls normalize_email prints:
Each EDGE line is one call and where it happens: find_user() calls normalize_email() on line 6 of app.py. EXTRACTED means the relationship was read from the source rather than inferred; see edges and provenance. Exact formatting can vary by release.

​
Whether two names connect

In the example project, graphify path "login" "normalize_email" prints:
A path needs both nodes and a chain of edges between them. No path is not proof that the two are independent. Add --undirected when you want connectivity rather than a directional path.

​
What a change can affect

In Graphify Cloud, open Graphs, search for the name, and inspect its neighbors. On a pull request, open Reviews and read the findings and the code the change can affect. A graph connection is evidence to investigate. It is not proof that behavior stayed the same.

Ask better graph questions

When to use query, path, and explain.

Query reference

Every flag graphify query accepts.