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/<branch>, 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.
Examples
ezgh build plan
ezgh build plan --commit 4f2a9c1 --ref refs/heads/mainFlags
| 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.