From 48a86374cb9242e4a91134b730afbb715a0a0dca Mon Sep 17 00:00:00 2001 From: Markus Neusinger <2921697+MarkusNeusinger@users.noreply.github.com> Date: Fri, 28 Aug 2026 23:38:19 +0200 Subject: [PATCH 1/2] docs(open-pr): watch the regional Cloud Builds, not the global list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The deploy-app / deploy-api triggers are regional (europe-west4). The skill's post-merge watch ran `gcloud builds list` without --region and got a handful of months-old global builds — all SUCCESS, none from today — which reads like "nothing was triggered" while both deploys were already done; the #10808 follow-through polled that list for 20 minutes. Name the region, add a SHORT_SHA column to match against the merge commit, and record the trap as a gotcha. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_016joUzstV3siE3WqJtbcych --- .claude/skills/open-pr/SKILL.md | 13 +++++++++++-- CHANGELOG.md | 5 +++++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/.claude/skills/open-pr/SKILL.md b/.claude/skills/open-pr/SKILL.md index f1f4ef5fc2..281add364e 100644 --- a/.claude/skills/open-pr/SKILL.md +++ b/.claude/skills/open-pr/SKILL.md @@ -183,10 +183,19 @@ When such paths merged, watch until the build succeeds — a red Cloud Build means production did NOT update even though the PR was green: ```bash -gcloud builds list --limit 3 -gcloud builds log # on failure +gcloud builds list --region=europe-west4 --limit 3 \ + --format='table(id,status,createTime,substitutions.TRIGGER_NAME,substitutions.SHORT_SHA)' +gcloud builds log --region=europe-west4 # on failure ``` +The `--region` flag is load-bearing: the `deploy-app` / `deploy-api` +triggers are **regional** (europe-west4), and the global `gcloud builds +list` answers with a handful of months-old global builds — all +`SUCCESS`, none from today — which reads like "nothing was triggered" +while both deploys are already done (2026-08-28, #10808 follow-through: +a 20-minute poll on the global list never saw the builds). Match the +`SHORT_SHA` column against the merge commit before trusting a row. + ## Gotchas - **`isOutdated` ≠ `isResolved`.** A fix-push can outdate a Copilot diff --git a/CHANGELOG.md b/CHANGELOG.md index 517a8c4267..fd08972692 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -211,6 +211,11 @@ aggregate instead: an italic *Catalog* line at the end of the version section an ### Changed +- **`open-pr` skill: the post-merge Cloud Build watch names the region** — `gcloud builds + list` without `--region=europe-west4` answers with months-old global builds (all `SUCCESS`, + none from today), which reads like "nothing was triggered" while both regional deploys are + already done; the #10808 follow-through polled that list for 20 minutes. The command now + carries the region and a `SHORT_SHA` column to match against the merge commit. - **`babysit-pipeline`'s gap-backfill guidance corrected against a completed run** — the section shipped in #10628 was written mid-backfill and three of its claims did not survive the rest of it. The halt-on-cluster threshold counted raw failed runs, but one From 8d573b8b84453f5271dab7e3f91c0a0188c96e9d Mon Sep 17 00:00:00 2001 From: Markus Neusinger <2921697+MarkusNeusinger@users.noreply.github.com> Date: Fri, 28 Aug 2026 23:38:50 +0200 Subject: [PATCH 2/2] docs: add PR reference to the changelog entry Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_016joUzstV3siE3WqJtbcych --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index fd08972692..0e8380333b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -215,7 +215,7 @@ aggregate instead: an italic *Catalog* line at the end of the version section an list` without `--region=europe-west4` answers with months-old global builds (all `SUCCESS`, none from today), which reads like "nothing was triggered" while both regional deploys are already done; the #10808 follow-through polled that list for 20 minutes. The command now - carries the region and a `SHORT_SHA` column to match against the merge commit. + carries the region and a `SHORT_SHA` column to match against the merge commit (#10809). - **`babysit-pipeline`'s gap-backfill guidance corrected against a completed run** — the section shipped in #10628 was written mid-backfill and three of its claims did not survive the rest of it. The halt-on-cluster threshold counted raw failed runs, but one