Oko/Docs

Command reference

oko defects found-in

Corrects the revision a defect was found in. A defect recorded after its repair was committed often names the repair itself as where it was found; a revision cannot repair what it is recorded as containing, so Tama's build gate counts such a defect as unrepaired until the revision that still had it is named.

Invocation#

Command
oko defects found-in <id> --revision <repository>@<revision> --reason TEXT [--json]

Inputs and options#

  • The defect id; --revision as <repository>@<revision>, verified against the workshop's checkout; --reason says why the recorded revision was wrong.

Output and state effect#

  • Replaces the found-in revision, keeps the old one as a dated note `recorded first as found in <old>: <reason>`, and prints `<id> found in <repository>@<revision>`. Naming the revision already recorded changes nothing.

Refusals and safe exits#

  • `oko defects found-in requires <id>`, `oko defects requires --revision <text>`, `oko defects requires --reason <text>` (exit 2); a revision the checkout does not hold is refused by the same check as `repaired`.
  • `defect <id> was already closed by <revision>`; `<revision> is recorded as the repair of defect <id>; it cannot also be where the defect was found`; `no defect with id <id> is registered`.

CLI reference#