Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: mention --graph on graphs page #9661

Merged
merged 1 commit into from
Jan 3, 2025
Merged

docs: mention --graph on graphs page #9661

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/repo-docs/core-concepts/package-and-task-graph.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@ description: Turborepo builds a Task Graph based on your configuration and repos
---

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

## Package Graph

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

In `turbo.json`, you express how tasks relate to each other. You can think of these relationships as
dependencies between tasks, but we have a more formal name for them: the Task
Graph.
dependencies between tasks, but we have a more formal name for them: the Task Graph.

<Callout type="good-to-know">
You can generate a visualization of the task graph for your tasks using [the
`--graph` flag](/repo/docs/reference/run#--graph-file-type).
</Callout>

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