From cc9ed2f2dec7d1f774ac34c89632c568108dc0af Mon Sep 17 00:00:00 2001 From: Erich Blume Date: Fri, 20 Feb 2026 10:14:44 -0800 Subject: [PATCH] Mikado: add push-after-every-iteration to git discipline Co-Authored-By: Claude Opus 4.6 --- docs/how-to/agent-change-process.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/how-to/agent-change-process.md b/docs/how-to/agent-change-process.md index 2007abc..d086fe9 100644 --- a/docs/how-to/agent-change-process.md +++ b/docs/how-to/agent-change-process.md @@ -113,7 +113,8 @@ tags: ### Git Discipline - Single feature branch per C1/C2 change -- **Create a PR early** — open a draft PR after the first doc commit so the user can review the Mikado graph as it evolves between iterations. Push doc updates after each attempt cycle. +- **Create a PR early** — open a draft PR after the first doc commit so the user can review the Mikado graph as it evolves between iterations. +- **Push after every iteration** — after completing a leaf node or documenting a failed attempt, push to origin. This is the save point for multi-session work. - Amend a single working commit as you iterate; keep the branch history clean - GitOps requires pushing to test — if a pushed commit breaks, revert it promptly - Commit doc updates noting what was learned from failures