Lock contention during automatic garbage collection in shared repositories
The goal is to determine whether Git's automatic garbage collector can safely run alongside concurrent fetch or push operations in a shared repository without introducing latency spikes or lock failures. Git describes gc.auto as a threshold-based trigger, but it does not guarantee serialization of repository writes. When multiple Git processes access the sam
git