Skip to content

Commit 31feea8

Browse files
committed
docs: Mention --graph on graphs page.
1 parent 3543736 commit 31feea8

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

docs/repo-docs/core-concepts/package-and-task-graph.mdx

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ description: Turborepo builds a Task Graph based on your configuration and repos
44
---
55

66
import { File, Folder, Files } from '#/components/files';
7+
import { Callout } from '#/components/callout';
78

89
## Package Graph
910

@@ -14,8 +15,12 @@ This sets the groundwork for the Task Graph, where you'll define how **tasks** r
1415
## Task Graph
1516

1617
In `turbo.json`, you express how tasks relate to each other. You can think of these relationships as
17-
dependencies between tasks, but we have a more formal name for them: the Task
18-
Graph.
18+
dependencies between tasks, but we have a more formal name for them: the Task Graph.
19+
20+
<Callout type="good-to-know">
21+
You can generate a visualization of the task graph for your tasks using [the
22+
`--graph` flag](/repo/docs/reference/run#--graph-file-type).
23+
</Callout>
1924

2025
Turborepo uses a data structure called a [directed acyclic graph (DAG)](https://en.wikipedia.org/wiki/Directed_acyclic_graph) to
2126
understand your repository and its tasks. A graph is made up of "nodes" and

0 commit comments

Comments
 (0)