Expand description
A feature’s code as a person reads it: what its branch changed
since it forked — by commit, by file — and its files. The revision is
never the caller’s: it is the feature’s branch, or HEAD before
speccoder worked on it; a file is read only when the tree lists it.
Structs§
- Changes
- What the feature’s branch changed since it forked.
- Commit
- One commit of the feature’s branch.
- File
- One changed file.
- Worktree
Entry - One path of a
WorktreeView. - Worktree
View - What git does not show at the feature’s revision: the worktree’s untracked, ignored and modified paths, and what of it would stop a run.
Constants§
- FILE_
LIMIT - The largest file shown.
- PATCH_
LIMIT - The largest patch sent whole.
Functions§
- changes
- What the feature’s branch changed since it forked from
HEAD. - file
- One file at the feature’s revision: its text, or why not (not in the tree, binary, too large).
- fix_
setup - Fixes the setup that stops a run, in the checkout at
root, on the person’s command: a lockfile only the worktree’s checks wrote is copied over, build output is added to.gitignore, and exactly those files and the uncommitted configuration are committed (speccoder: setup). - setup_
remedy - The fix of what in the setup stops a run, as an interface offers it:
Nonewhen nothing does. - tree
- The files at the feature’s revision (at most 20 000).
- worktree_
file - An untracked file of the feature’s worktree, read from disk: its text,
or why not. Only what
worktree_viewlists as untracked. - worktree_
view - The feature’s worktree as it is on disk, beyond what git committed.