Tag
4 posts
git bisect run in a pipeline is one line and almost useless on its own: the work is making an arbitrary historical commit provisionable, buildable and testable — and reading the loop's own exit status honestly.
A worktree per task stops two coding agents from overwriting each other's files. It does not isolate the approvals, hook paths and untracked instructions that decide what an agent does next — nor the lifecycle a headless run leaves behind.
Bisect halves an interval and asks your predicate one question per step. On the same history, a broad predicate and a targeted one returned different culprits — both with exit status zero.
One repository, several working directories on a single object store. What git worktree shares, what it isolates, the branch mutex, the lifecycle, relative paths, and the submodule limits the manual still calls incomplete.