Compile and expand a pipeline config file

## Usage

`circleci config process <path> [flags]`

## Arguments

`<path>` is the path to a pipeline config file to compile,
for example, `.circleci/config.yml`. Pass `-` to read the config
from stdin.

## Flags

| Flag                           | Description                                                                                  |
| ------------------------------ | -------------------------------------------------------------------------------------------- |
| `-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 |
| `--pipeline-parameters string` | Pipeline parameters as a YAML map or path to a YAML file                                     |

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

## Examples

- Process the default config: 
  `circleci config process .circleci/config.yml`
- Process with pipeline parameters: 
  `circleci config process .circleci/config.yml --pipeline-parameters 'env: staging'`
- Process against a specific org (otherwise inferred from the git remote): 
  `circleci config process .circleci/config.yml --org gh/myorg`
- Read from stdin: 
  `cat .circleci/config.yml | circleci config process -`

## Details

Compile a CircleCI pipeline config and print the fully expanded YAML —
orbs inlined, matrices expanded, parameters resolved.

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.

