From 1f5d881012219353b49e9ff66c32febe247dca15 Mon Sep 17 00:00:00 2001 From: Anthony Miller Date: Tue, 26 May 2026 12:03:51 -0700 Subject: [PATCH] =?UTF-8?q?docs(cache):=20add=20progress-tracker=20update?= =?UTF-8?q?=20to=20=C2=A74.7=20on-merge=20checklist?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After a PR merges into the plan branch, the agent now also updates the progress tracker that lives in the plan-branch PR's description (the long-lived PR with base `main` and head `cache-rewrite/phase-1-plan`). This keeps a single management-visible source of truth in sync with the merged stack state, without requiring the manager to inspect git or the PR list directly. Co-Authored-By: Claude Opus 4.7 (1M context) --- apollo-ios/Design/cache-rewrite-phase1-execution.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/apollo-ios/Design/cache-rewrite-phase1-execution.md b/apollo-ios/Design/cache-rewrite-phase1-execution.md index 9f7d60b46..aef90d45c 100644 --- a/apollo-ios/Design/cache-rewrite-phase1-execution.md +++ b/apollo-ios/Design/cache-rewrite-phase1-execution.md @@ -169,7 +169,8 @@ Quality gates per §5 must all be green before opening the PR. If any gate fails 1. Pull the merged change into local `main` (or the merged base). 2. Rebase the next stacked PR onto the new base; resolve any conflicts. 3. Re-verify the next PR's quality gates after rebase. -4. Continue with the next PR. +4. Update the progress tracker in the plan-branch PR's description (the long-lived PR with base `main` and head `cache-rewrite/phase-1-plan`): flip the merged PR's row from 🟡 to ✅, fill in the merge date, and adjust per-phase / overall percentages. Done via `gh api repos/.../pulls/{plan-PR-number} -X PATCH -F body=@…` per the dev-repo's GitHub-CLI workaround in `CLAUDE.md`. +5. Continue with the next PR. ## 5. Quality gates