Command reference
oko defects naming
Lists every open defect whose found-in, repair or attempted repair names a commit. The Git gate can see claims as well as verified repairs before rewriting history.
Invocation#
oko defects naming <repository>@<commit> [--json]Inputs and options#
- The repository and full or short commit id; --json prints {id, product, field, recorded}. The field is found-in or repaired, including an unqualified claim under the latter protocol identity.
Output and state effect#
- Reads every open defect and prints one line per entry naming the commit, `<id> <product> <field> <recorded>`, then `<n> register entr(ies) name <revision>`. Changes nothing.
- A commit no entry names prints only the count line with 0; a short id names the same entries its full id names.
Refusals and safe exits#
- A subject without `@`, or one whose commit is empty or not hexadecimal, is refused: `oko defects naming takes <repository>@<commit>; got <subject>` or `takes a commit id after @` (exit 2). Any flag other than --json is refused by name.
- OkoKit's `OkoDefectRegister.naming(revision:)` and the native API action `naming` answer the same rows for Oko Desktop.
- The real CLI journey in tests/defects/rebased.rs records a defect against commits of a checkout of its own and asks by full and short id, for the found-in, the repair, an unrecorded commit and a subject that is not a commit.