Stefan Haller d19af37ee7 Tell git where the repo is when it can't find it itself ... git finds a repo by looking for a .git in the directory a command runs in. Lazygit runs its commands in the work tree, so that normally works — but not when the git dir lives somewhere else entirely, which is what core.worktree and --work-tree are for. Lazygit chdir'd into such a work tree and then ran commands that couldn't see any repo from there, so opening a repo with core.worktree set panicked on startup. It only worked with --git-dir because that leaves GIT_DIR in the environment for every command to inherit. Work out at startup whether git can find the repo from its work tree, and when it can't, put GIT_DIR and GIT_WORK_TREE on every command the repo's builder produces. As with the working directory the builder pins (527124d0e0), these also go into the process env — subprocesses don't come through the builder — but the commands don't read them from there, because the process env belongs to whichever repo we have switched to since. Working out whether git can find the repo means asking git, rather than reading the .git file, whose contents can spell the same directory differently than git does. The extra query is skipped for a repo whose git dir is simply its .git directory, which is nearly all of them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-08-08 11:15:01 +02:00
..
env.go	Tell git where the repo is when it can't find it itself	2026-08-08 11:15:01 +02:00