Do not record a no-op consistency sync as a fix.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Multi-Context Image / build-and-push (push) Successful in 1m11s

A binding put that only refreshes the sync timestamp, a push that reports the remote is already current, and a C-11 skip on a finished workplan are not repairs. Leave those out of FIXES APPLIED so a clean second run stays clean.

Assistant: grok
Assistant-Session: 01a16071-5425-78d3-80b4-20fe2ee30f0a
This commit is contained in:
tegwick 2026-10-22 09:28:10 +02:00
parent 64d698e65d
commit bd6fd62b0a
5 changed files with 130 additions and 10 deletions

View file

@ -74,7 +74,12 @@ def push_ff(repo_path: str) -> tuple[bool, str]:
capture_output=True, text=True, timeout=PUSH_TIMEOUT_SECONDS,
)
if result.returncode == 0:
return True, result.stdout.strip() or "pushed"
detail = "\n".join(
part.strip() for part in (result.stdout, result.stderr) if part and part.strip()
)
if "everything up-to-date" in detail.lower():
return True, "Everything up-to-date"
return True, detail or "pushed"
return False, result.stderr.strip() or "push failed"
except subprocess.TimeoutExpired:
return False, "push timed out; remote outcome unverified; inspect the remote ref before retrying"