List triggers for a pipeline definition

## Usage

`circleci project trigger list [flags]`

Aliases: `circleci project trigger ls`

## Flags

| Flag                              | Description                                                                       |
| --------------------------------- | --------------------------------------------------------------------------------- |
| `--jq string`                     | Process values from the response using jq syntax (see `circleci help formatting`) |
| `--json`                          | Output as JSON                                                                    |
| `--pipeline-definition-id string` | Pipeline definition ID (required)                                                 |
| `--project string`                | Project slug (e.g. gh/org/repo); defaults to git remote                           |
| `--project-id string`             | Project UUID (overrides --project)                                                |

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

## Examples

- List triggers for the current repository's project: 
  `circleci project trigger list --pipeline-definition-id a1b2c3d4-...`
- List triggers for a specific project: 
  `circleci project trigger list --project gh/myorg/myrepo --pipeline-definition-id a1b2c3d4-...`
- Output as JSON for scripting: 
  `circleci project trigger list --pipeline-definition-id a1b2c3d4-... --json`

## Details

List all triggers attached to a pipeline definition.

--pipeline-definition-id is required. In a terminal it will be prompted
interactively if omitted; in non-interactive mode (CI, agents) it must
be passed as a flag.

JSON fields: id, created_at, event_name, event_preset, config_ref, checkout_ref, disabled, event_source.provider, event_source.repo.external_id, event_source.repo.full_name

