kapi commit

$ kapi commit

Write the unit state recorded since the last commit into the project's committed record: the JSON Lines shards under .kapi/state/ that git tracks.

Recording a review and publishing it are separate acts. The state record is durable the moment it is written; committing is what puts it in the record a reviewer reads, so a run of automated approvals does not land in the tracked record before anyone has looked at it.

The working set is rebuilt from the record this checkout holds whenever the two have parted, which is what switching branches does to them. Staged decisions cross that rebuild and are reported, because they were made against the record of another branch.

'--dry-run' reports what would be written and writes nothing. 'kapi status' reports what is staged.

Commandcommit

Groupwork

Try it

Runs in your browser against a small sample file. Edit the command before running, or press Run to execute it as shown.

$ kapi commit

Flags

Flag	Type	Default	Description
--dry-run	bool	false	report what would be committed and write nothing
--project, -p	string		path to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted)

← Back to the Command Reference