Skip to main content

Crate jouet_git

Crate jouet_git 

Source
Expand description

The git recipes behind jouet commit, jouet review-package, jouet handoff and jouet pickup.

Everything shells out to the git on PATH, so hooks, config, attributes and credentials behave exactly as they do for the agent’s own git calls. Pathspecs are always literal (--literal-pathspecs): a name such as *.rs or :/ means that file, never a pattern or the whole tree.

Modules§

agent
Which agent is running, as far as the environment says, and the commit trailers that follow from it.
claim
Advisory claims between agent sessions on one machine, for jouet claim: a session says it is working on some paths, and the others are told before they edit or commit them.
commit
jouet commit PATH... -m MSG: commit only the named paths.
conventional
Conventional-commit subjects: whether a repository asks for them, and what is wrong with a subject that is not one.
handoff
jouet handoff and jouet pickup: facts about a checkout, written for the next session, and a check that they still hold.
notes
Lines of text kept as git notes on commits, under one notes ref, the way tak keeps its measurements:
review
jouet review-package BASE HEAD: one file holding everything a reviewer needs for a range of commits: the commits, a diffstat, and the full diff with extra context.
session
The last test, lint and build runs of an agent session, as jouet setup’s hooks record them in $XDG_STATE_HOME/jouet/sessions/ID.json, by the work tree each ran in: {"trees": {"/src/app": {"runs": {"test": {"command": "cargo test", "exit_code": 0}}}}}.
stack
Stacked branches, for jouet stack: whether each layer really contains the layer below it, by ancestry and by content.
status
The state of a work tree from git status --porcelain=v2 --branch, as the rules’ jouet.git.state() probe and the routines’ git.state() report it.

Structs§

Error
Why a recipe stopped: the exit code to leave with, what went wrong, and what to change.
Git
git, run in one directory.