---
title: "ezgh build validate"
description: "Check a build file."
---

> 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 validate

{/* 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 validate [file]
```

Check a build file: .ezgh/build.yaml of the checkout, or the file named. Every problem is printed with its place in the file, the reason and an example that would be accepted; the exit code is 1 when there is one.

The format is checked here, without a request. When you are logged in, what the file names (Bots, secrets, buckets, clusters and images) is then looked up with your own credential. A build's repository is not: it is created on the first push.

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

## Examples

```sh
ezgh build validate
ezgh build validate --json
```

## Flags

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-validate/index.mdx
