Stefan HallerandClaude Fable 5 568a4276d7 Pin the cached git config's commands to the repo directory ...

The cached git config runs its `git config` reads through raw
exec.Command calls, outside the pinned git command builder, so they
followed the process working directory. A cache miss on a stale
instance — one still in use by a refresh that crossed a repo switch —
would therefore read the new repo's local config while computing data
for the old one. Give the cache a directory, set once by NewGitCommand
right after it determines the repo paths (the object is created fresh
for every repo switch, so no cross-repo cache invalidation is needed),
and run every config command there.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-20 17:07:39 +02:00

..

cached_git_config_test.go

Pin the cached git config's commands to the repo directory

2026-07-20 17:07:39 +02:00

cached_git_config.go

Pin the cached git config's commands to the repo directory

2026-07-20 17:07:39 +02:00

fake_git_config.go

Pin the cached git config's commands to the repo directory

2026-07-20 17:07:39 +02:00

get_key.go

Enable errorlint linter, and fix warnings

2025-06-30 18:30:11 +02:00