Command reference
oko oneoff check
Runs every rule's example past each gate the installed Tama registry binds to a bash payload and reports what each refused. A gate that refuses the control command `echo ok` is answering about this context, not about a shape, and is reported apart.
Invocation#
oko oneoff check [--json]Inputs and options#
- None; the gate binaries come from the installed registry, or one named in the gate environment variable to check a build before it is installed.
Output and state effect#
- Runs the gates; prints the verdicts.
Refusals and safe exits#
- `no gate is bound to a bash payload on this machine: none of these shapes is refused before it runs. Install the hooks with <install command>, or name one binary in <variable> to check a build before it is installed.`
- A gate that cannot be run is not counted as letting a shape through: `hook gate <path> cannot be started: <cause>`, `hook gate <path> could not be waited on: <cause>`, `hook gate <path> was not handed the payload of `<example>`: <cause>` and `hook gate <path> neither allowed nor refused `<example>`: it ended with <status>: <stderr>`. A gate that closes its input without reading the payload answers as itself.