This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

abcd's lane worktrees and restarts in a repository that uses Git LFS hold LFS pointer text instead of the real files. Lane creation (`git worktree add`, internal/core/implement/loop/lane.go) and a restart's `reset --hard` (restart.go) run through gitutil's isolated environment, which sets GIT_CONFIG_GLOBAL=/dev/null (internal/gitutil/repo.go), so the filter that a normal, global `git lfs install` defines is never seen and nothing is smudged. Reproduced 2026-10-11 with git-lfs 3.7.1: in a repository whose image is tracked by LFS, the person's own `git worktree add` writes the image's bytes, while the same command with GIT_CONFIG_GLOBAL=/dev/null writes `version https://git-lfs.github…` pointer text. The implementer then builds and tests against placeholders. This is abcd changing how a repository works, which the security scope rule (principle abcd-fixes-what-it-adds) forbids.

issueresolvedmajoriss-2610111729375108

abcd's lane worktrees and restarts in a repository that uses Git LFS hold LFS pointer text instead of the real files. Lane creation (git worktree add, internal/core/implement/loop/lane.go) and a restart's reset --hard (restart.go) run through gitutil's isolated environment, which sets GIT_CONFIG_GLOBAL=/dev/null (internal/gitutil/repo.go), so the filter that a normal, global git lfs install defines is never seen and nothing is smudged. Reproduced 2026-10-11 with git-lfs 3.7.1: in a repository whose image is tracked by LFS, the person's own git worktree add writes the image's bytes, while the same command with GIT_CONFIG_GLOBAL=/dev/null writes version https://git-lfs.github… pointer text. The implementer then builds and tests against placeholders. This is abcd changing how a repository works, which the security scope rule (principle abcd-fixes-what-it-adds) forbids.

Frontmatter

idiss-2610111729375108
typeissue
lifecycleresolved
severitymajor

mentions2