---
title: "ezgh build plan"
description: "Say what a run would do, task by task."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ezgh build plan

{/* Generated by ezgh-cli's internal/tools/clidocs from the ezgh command tree. Don't edit: change the command's help in ezgh-cli and regenerate. */}

```sh
ezgh build plan [--connection c] [--commit sha --ref r] [flags]
```

Say what a run would do: which tasks would run, which would be skipped by content (cached) and which by their only rule, each with the reason.

The plan is computed here from your checkout: the working tree as it is, on refs/local/&lt;branch&gt;, or with `--commit` a commit's files on the ref given with `--ref` (a full ref, like refs/heads/main). Only each task's key is sent; no file leaves your machine.

Part of [`ezgh build`](/cli/reference/build).

## Examples

```sh
ezgh build plan
ezgh build plan --commit 4f2a9c1 --ref refs/heads/main
```

## Flags

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--commit` | string |  | plan this commit instead of the working tree (with `--ref`) |
| `--connection` | string |  | the connection, when the project has more than one |
| `--ref` | string |  | the full ref the commit is pushed to |

Inherited from parent commands:

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--dir` | string | `.` | the repository's checkout (any directory inside it) |
| `--json` | boolean |  | print JSON, as -o json does |

This command also takes the [global flags](/cli/reference#global-flags).

Source: https://docs.ezghcloud.com/cli/reference/build-plan/index.mdx
