Expand description
Which commit command lines the commit service covers, and the message they stand for.
What:
Which git commit command lines the resident service lands, and the message such a line stands for.
Why:
The service lands the scoped commit an agent or a person types most (git commit -m <message> -- <paths>), with the
options that only shape the message or the identity: -F <file>, --author, --date, --trailer, --cleanup,
--allow-empty-message. Every other option (amend, editor, signing, templates, sign-off) still goes through the
transaction until the service covers it, so this module answers “is this line one the service covers” before anything
is prepared, and builds the message with the clean-up Git applies when no editor opens.
In TS you’d write (pseudocode):
const parsed = parseServiceCommit(args); // undefined when the line needs native git commitStructs§
- Service
Commit Args - What a covered command line asked for.
Enums§
- Fixup
Kind - Which message prefix
--fixupand--squashmake.
Functions§
- cleanup_
message - What: The commit message Git makes of the given texts when no editor opens. Why: Each text is a paragraph; Git strips trailing whitespace from every line, drops leading and trailing blank lines, squeezes runs of blank lines into one and ends the message with a newline. An empty result is no message.
- parse_
service_ commit - What:
Reads the arguments after
commitand says whether the service covers them. Why: Anything not listed here is refused, so a new Git option is never silently dropped.