Commit
The commit as a value: the scope vocabulary this repository's own history yields, what the working tree would commit and how it divides, and the verdict on one message against the repository's commit policy.
The commit as a value: the scope vocabulary this repository's own history yields, what the working tree would commit and how it divides, and the verdict on one message against the repository's commit policy.
- module commit
- builtin
- behaviorally_verified
- 4 capabilities
Capabilities
Each composed in this module's file; each with its own page.
commit.historyEvery commit in a git range against the commit policy, in one pass: how many were read, how many git composed and are exempt, how many carry an error, and every commit that has a finding with what it is. What the gate reads to refuse new debt, and what answers `is the history of this branch clean?` without a process per commit.query · behaviorally_verified · majordomus_commit_history · GET /api/v1/commit/historycommit.planThe working tree as git reports it — branch, upstream, divergence, every staged, unstaged and untracked path, and any merge or rebase in progress — divided into the commits the history's own scoping supports, each with the evidence for it, under a fingerprint of the repository, the worktree, HEAD and the exact change set, so that a plan acted on later can be refused rather than applied to a tree it was not made for.query · behaviorally_verified · majordomus_commit_plan · GET /api/v1/commit/plancommit.scopesEvery scope this repository's commit history uses, how often, and the directories each one is written about — learned from the history rather than declared in a table, so that a subsystem committed today is in the vocabulary today and one nobody has touched falls to the bottom on its own.query · behaviorally_verified · majordomus_commit_scopes · GET /api/v1/commit/scopescommit.validateOne message against this repository's commit policy: the grammar, the subject width, whether the scope is one the history uses, whether every record the message names exists, whether a fix carries a test, and whether a breaking change explains itself — as typed findings with severities, or an exemption for a subject git composed. The same verdict the commit-msg hook refuses with and the gate reads the history through.query · behaviorally_verified · majordomus_commit_validate · GET /api/v1/commit/validate