opschain approvals history

packs:change-governance

opschain approvals history [--mine] [--decided-by <user>] [--status <outcome>] [--target <path>] [--since <instant>] [flags]

Lists the decision history (ChangeGovernanceService.ListApprovalChecklists), newest decision first: every decided checklist you may see — the answer to "what did I approve in the past?" and, for the governance administrator, "who decided what?". The table is WHEN STATUS KIND TARGET ACTION RUN DECIDED BY NOTE:

• WHEN — the decision instant (the release for a released subject, the completion for an approved-held one, the finalisation for a rejection or timeout).
• STATUS — the outcome: approved (quorum complete — held for its window or released by approval), rejected, timed_out (the quorum TTL lapsed), break_glass (released without quorum) or pending.
• DECIDED BY — the approvers whose rows are live on any line (every line's approver on a multi-line checklist), plus the rejecter or break-glass releaser; your own decision is marked (you) — (incl. you) among several — and a timeout is nobody's (-).
• NOTE — the rejection or break-glass reason, else the approvers' comments.

Which checklists you see is the server's rule: those on targets you may read, those you decided yourself (an approver always sees what they decided, whichever line of the checklist they decided, even after their read on the target is withdrawn — the row is theirs), and — holding the oversight determination, readable on /governance/change or updatable on /admin (the governance administrator) — every decision in the estate. Without --mine the verb lists everything you may see; --mine narrows it to your own decisions.

-o json / -o yaml emit the typed entries under entries — each with its full checklist (lines, approval rows, clocks, fingerprint, the approval context), outcome, decided_at, decided_by, decided_by_you and note — beside nextPageToken, oversight (the listing was estate-wide) and decidedBy (the decider the listing was narrowed to).

The open checklists waiting on you are the inbox: opschain approvals list.

Flags

Flag	Meaning
--mine	Only your own decisions — checklists you approved a line of, rejected or break-glassed.
--decided-by <user>	Only the decisions of this username (cannot be combined with --mine naming someone else).
--status <outcome>	Only these outcomes (comma-separated or repeated): approved, rejected, timed_out, break_glass, pending. The default lists the four decided outcomes; pending is listed only when named.
--target <path>	Only subjects on this node path or inside its subtree.
--kind <kind>	Only this subject kind: change, workflow, trust_grant, agent_release or transport_grant.
--since <instant>	Only checklists that entered the funnel at or after the instant — RFC3339 (2026-10-17T00:00:00Z) or a duration ago (24h, 7d).
--until <instant>	Only checklists that entered the funnel at or before the instant (same forms).
--limit <n>	Rows per page (default 50; the server caps it at 1000). When more follow, the table ends with the --page-token to continue with.
--page-token <token>	Continue from a previous page's token.
--filter <column>[!]=<value>	Keep only rows matching the term (repeatable; terms AND). Columns are the printed table headers lowercased (spaces fold to _); * wildcards match the whole cell case-insensitively, != negates, commas mean any-of. Grammar: opschain docs cli.

Examples

# What did I approve, reject or break-glass?
opschain approvals history --mine

# The governance administrator: every decision on production this week
opschain approvals history --target /projects/limebank/environments/prod --since 7d

# Only the decisions a given approver made
opschain approvals history --decided-by sarah --status approved,rejected

Exit codes

Code	Meaning
0	Listed (an empty selection prints no decided approval checklists).
1	The read failed — the error names the server's Connect code and message.
2	Usage error, including a missing server target, a malformed --since/--until, or an unknown --status.