ek9_git_commit
Reports newSha and previousSha, branch, subject, changedFiles and changedFileCount; local history only, nothing is published until ek9_git_push.
When to use it
'Commit this' - one call with message; paths:[...] stages and commits in one step, all:true stages tracked edits, amend:true rewrites the last commit. The middle step of stage, commit, push.
When not to use it
- publishing to the remote - use
ek9_git_push. - staging without recording - use
ek9_git_add. - checking what would be committed - use
ek9_git_status.
Details
message is required unless amend:true (then omitted = keep the previous message). all:true stages tracked modifications only - a new file needs paths or ek9_git_add. Shas are the 8-hex short form shared across the family. A clean index is refused as nothing-to-commit with the route; a missing user.name/user.email is git's own refusal, surfaced under error.message.
Arguments
| Argument | Type | Required | What it is |
|---|---|---|---|
all | boolean | Stage every tracked modification first (git commit -a); untracked files are not included. Default false. | |
amend | boolean | Rewrite the previous commit instead of creating a new one. Default false. | |
message | string | Commit message. Required unless amend:true, which then keeps the previous commit's message. | |
paths | array of string | Workspace-relative paths to stage before committing (stage + commit in one call). |