Instrument your config for deploy tracking

## Usage

`circleci deploy init [flags]`

## Flags

| Flag                       | Description                                                                |
| -------------------------- | -------------------------------------------------------------------------- |
| `--component string`       | Service/component name (skips prompt)                                      |
| `--environment string`     | Default environment for jobs whose target can't be inferred (skips prompt) |
| `--pipeline-config string` | Path to CircleCI pipeline config file (default ".circleci/config.yml")     |

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

## Examples

- Interactive setup in the current repo: 
  `circleci deploy init`
- Skip the service-name prompt: 
  `circleci deploy init --component api`
- Fully non-interactive (supply both answers as flags): 
  `circleci deploy init --component api --environment production`
- Use a non-default config location: 
  `circleci deploy init --pipeline-config path/to/config.yml`

## Details

Set up deploy markers in .circleci/config.yml.

Scans the config for deploy-like jobs (names containing deploy,
release, publish, or ship), prompts for your service name and
target environment, then adds a log step to each deploy job.

The command is idempotent: running it twice on the same config
makes no duplicate changes.

Works offline — no API calls required.

