reseed: no-op guard — unchanged origin refs skip the PR #84

Merged
plat merged 1 commit from feat/reseed-noop-guard into main 2026-07-02 19:05:34 +00:00
Owner

A second dispatch racing a merged reseed produced an unmergeable binary-conflict PR (#83). The run now compares the fresh manifest's repo refs against the committed seed and exits 0 with a loud NO-OP when identical (explicit gitops_ref still forces). Live proof after merge: a plain dispatch should end in NO-OP with no PR.

🤖 Generated with Claude Code

A second dispatch racing a merged reseed produced an unmergeable binary-conflict PR (#83). The run now compares the fresh manifest's repo refs against the committed seed and exits 0 with a loud NO-OP when identical (explicit gitops_ref still forces). Live proof after merge: a plain dispatch should end in NO-OP with no PR. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Two reseeds from identical refs differ only in squash timestamps; the
second lands an unmergeable binary-conflict PR (observed: PR #83 vs merged
r25). Compare the new manifest's repo refs against the committed seed's and
exit 0 with a loud NO-OP line when equal (explicit GITOPS_REF still forces
a build — coordinated-release seeds are never no-ops).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
plat merged commit a6ee4cae20 into main 2026-07-02 19:05:34 +00:00
Sign in to join this conversation.
No description provided.