CLI reference
heddle commit
Shippedheddle commit [OPTIONS] Commit the current captured state to the authoritative Git checkout. Git Overlay only: this is the step that publishes captures into .git, and it is the step Native Heddle does not have.
Output text (default) · json
In Git Overlay, heddle capture records a Heddle state and heddle commit publishes it to the checkout's real .git. In Native Heddle there is no second step: capture alone saves source history.
heddle commit does not run your Git hooks. The binary states it in its own Behavior block, verbatim: Commits the complete captured tree and replaces the Git index with that tree. Git pre-commit and commit-msg hooks are not run. If your team relies on a pre-commit secrets scan or formatter, run it yourself — nothing else will.
There is also no staging area to select from. commit publishes the complete captured tree, which is whatever heddle capture saved, which is the whole unignored worktree. -m defaults to the current capture intent, so the common case is a bare heddle commit.
Flags
--message <message>, -m <message>- Git commit message. Defaults to the current capture intent.
Exit codes
Declared by this command's contract, verbatim. Anything not listed
contracts only to 0 on success and an unspecified
non-zero on failure. The full table
and the retry rule — in short, 75 is the only code that
is safe to retry.
0- Git checkpoint written or already current
65- repository mode or worktree preflight refused
74- io while writing Git state
Examples
The Git Overlay save loop
bash$ heddle capture -m 'add login route'$ heddle commit# no pre-commit or commit-msg hook runs here