Govern config with Rego security policies

## Usage

`circleci policy <command> [flags]`

## General Commands

| Command  | Description                                       |
| -------- | ------------------------------------------------- |
| `decide` | Evaluate a config against remote policies         |
| `eval`   | Evaluate a raw OPA query against policies locally |
| `push`   | Push a policy bundle to CircleCI                  |
| `test`   | Run policy tests                                  |

## Targeted Commands

| Command | Description                                       |
| ------- | ------------------------------------------------- |
| `diff`  | Show diff between local and remote policy bundles |
| `fetch` | Download the remote policy bundle                 |
| `logs`  | Get policy decision logs                          |

## Subcommands

| Command    | Description                        |
| ---------- | ---------------------------------- |
| `settings` | Manage policy enforcement settings |

## Flags

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

## Details

Manage security policies.

Policies are written in Rego and evaluated against pipeline configs to
enforce organizational security rules.

Most commands require --org, your organization's slug (e.g. gh/acme) or UUID,
found at <https://app.circleci.com/settings/organization>.

