Validate a pipeline config file

## Usage

`circleci config validate [<path>] [flags]`

## Arguments

`<path>` is the pipeline config file to validate, by default
`.circleci/config.yml`. Pass `-` to read the config from stdin.

## Flags

| Flag                  | Description                                                                                  |
| --------------------- | -------------------------------------------------------------------------------------------- |
| `-c, --config string` | Path to config file (use "-" for stdin) (default ".circleci/config.yml")                     |
| `--json`              | Output as JSON                                                                               |
| `-n, --next`          | Enable config next which previews upcoming potentially breaking config changes               |
| `--org string`        | Organization slug (e.g. gh/myorg) or UUID for private orb resolution; defaults to git remote |

Global flags: `--debug`, `--no-color`, `-q, --quiet` — see `circleci --help`.

## Examples

- Validate the default config file: 
  `circleci config validate`
- Validate a specific file: 
  `circleci config validate path/to/config.yml`
- Validate against a specific org (otherwise inferred from the git remote): 
  `circleci config validate --org gh/myorg`
- Validate and output as JSON: 
  `circleci config validate --json`

## Details

No API token is required; without one, only public orbs resolve.
Private and namespaced orbs need a token and resolve against your org, taken
from --org, a 'circleci project link' binding, or the git remote, in that order.

JSON fields (--json): valid (bool), compiled_yaml (string, when valid), errors (array of compilation messages, when invalid)

