b8e ticket list
List violation tickets
Options
Section titled “Options”| Option | Takes | Default | Description |
|---|---|---|---|
-f, --format <format> | value | pretty | output format |
--project <id> | value | narrow to one project (default: ask, or the whole org) | |
-L, --limit <n> | value | 50 | maximum number of tickets to fetch |
--first <n> | value | max tickets to fetch | |
--ci | boolean | never ask which project (use —non-interactive) |
b8e ticket list --help
Section titled “b8e ticket list --help”Identical to what the terminal prints — both are rendered from the same commander definition.
Usage: b8e ticket list|ls [options]
List violation tickets
Options: -f, --format <format> output format (choices: "pretty", "json", default: "pretty") --project <id> narrow to one project (default: ask, or the whole org) -L, --limit <n> maximum number of tickets to fetch (default: 50) -h, --help display help for command
EXAMPLES # Tickets for the current organization $ b8e ticket list
# Feed a script — the payload is on stdout, every human line on stderr $ b8e ticket list --format json | jq '.[].url'
INHERITED FLAGS --org <id|slug|name> organization context [$BINCLUSIVE_ORG_ID] -y, --yes skip all prompts and accept defaults --non-interactive never prompt; fail instead of asking --progress <mode> how progress is reported -q, --quiet suppress progress output (same as --progress quiet) --no-color disable color -v, --verbose verbose diagnostics -V, --version print the CLI version -h, --help show help for command