seat: the host's git runs no background maintenance in a role clone (row 118, #1612)

Candidate manifest eeb67779c919b7c1f25b4449df7207d85634e5175b16eef315346cf5a284c63c from Darkwing's round 1 packet (5a68df727), on BASE 2727dd3ec. No manifest path changed between BASE and the landing target. Dewey approved in 28479, with no blocking or doc-only findings. Sage reran the full gate at the landing target with the candidate applied. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-14 14:52:07 -05:00
parent a076f28c00
commit c2525dd335
3 changed files with 79 additions and 1 deletions
@@ -67,6 +67,11 @@ const SAFE = [
  "-c", "protocol.allow=never",
  "-c", "protocol.file.allow=always",
  "-c", "submodule.recurse=false",
+  // A fetch or a merge would start `git maintenance run --auto`, which
+  // detaches from the call's process group and repacks the clone after the
+  // call has returned. gc.auto=0 also stops a gc --auto that runs anyway.
+  "-c", "maintenance.auto=false",
+  "-c", "gc.auto=0",
 ];

 // The environment git runs with: the host's PATH and nothing else of it.