jadpo approval
On this page
Explain a change, decisions first.
Writes the approval report a reviewer reads (area 17): build/review/approval.md and approval.json, the difference between this change and its before side, the default branch at its merge base, or the branch or commit --before names. It builds the before side with this compiler and keeps its manifest in build/before/jadpo check is what fails until each decision has its acceptance.
jadpo approvalFlags
--before <ref>: The branch or commit to compare with
On every command
--json: Print data for tools instead of text--help: Show every flag, with examples--color <when>: Choose when to use colour
jadpo approval --json writes one JSON document to standard output instead of text, with the same exit code. The document has schemaVersion, command ("approval"), ok, data (what the command produced, null when it failed) and diagnostics (each error with its rule, reason, next and help). A command that needs a terminal refuses --json and names the flags that do the same job.
Examples
# Explain this branch's change against the default branchjadpo approval# Explain what changed since a deployed commitjadpo approval --before 8d113e6
Errors
cli.approval_arguments: Ajadpo approvalcommand is given an argument it doesn't take, names a--beforegit doesn't know, or has nothing to compare withacceptance.base_missing: Base commit the change is compared with isn't in this clonetoolchain.artifact_write_failed: A file Jadpo writes for you, such as a record, couldn't be written, usually because it or its folder is read-onlytoolchain.project_not_found: You ran a command that works on a project in a folder with noapp.jadpo, in it or in any folder above it
Markdown for agents: /docs/jadpo-approval.md.Built from Jadpo main at e00e61f.