Oko/Docs

Command reference

oko frustration answer

Records the revision that answered the moment's cause.

Invocation#

Command
oko frustration answer <id> --revision <repository>@<revision> --detail TEXT [--json]

Inputs and options#

  • The moment id, the revision and what it changed.

Output and state effect#

  • Stores the answer and prints `answered <id> by <revision>: <detail>`.

Refusals and safe exits#

  • `oko frustration answer requires <id>`, `oko frustration requires --revision <text>`, `oko frustration requires --detail <text>` (exit 2); `entry <id> has no cause named yet, so there is nothing to answer: name it with `oko frustration cause <id> --cause <text>``; `entry <id> was already answered by <revision>`.

CLI reference#