CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-09-12 16:08:59 +02:00
Code Issues Packages Projects Releases Wiki Activity

chore: zero-heads warning names the benign cause too; digest path declaration made load-bearing; ratchet re-capture

Browse Source 
- The ls-remote zero-heads warning no longer accuses an empty remote of
  running a laundering shim.
- instructionTier.rulesFile now must equal the generator's DIGEST_RELPATH
  (and setup must print it) — the declaration fails with the real path
  instead of lying silently.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-08-29 05:58:14 +00:00
co-authored by Claude Fable 5
parent 5ed46193f1
commit cb8bd9b98d
3 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bin/gstack-next-version
+1 -1
View File
@@ -550,7 +550,7 @@ function fetchGitClaimed(
// `upstream` remote's branches are not claims against OUR queue).
warnings.push(
lsOk
? "git ls-remote origin exited 0 but advertised zero heads (exit-code-laundering shim suspected); " +
? "git ls-remote origin exited 0 but advertised zero heads (an empty remote, or an exit-code-laundering git shim); " +
"using stale local refs/remotes/origin — branches deleted on the remote may still be counted as claims (run `git fetch --prune origin` to refresh)"
: "git ls-remote origin failed; using stale local refs/remotes/origin — " +
"branches deleted on the remote may still be counted as claims (run `git fetch --prune origin` to refresh)",