cctest-recipe-upstream: always emit step 0 fetch-from-mirror commands for the operator

2026-09-14 16:57:07 +00:00
parent d48e47adfe
commit 7934367f15
2 changed files with 25 additions and 0 deletions
@@ -78,6 +78,19 @@ not the test server — so it can run either way. Probe, then follow that branch
  4. Everything else in the canonical script (origin/dev remote setup, release recommendation,
     emitted next-steps) is identical.

+Every time the branch was prepared **here**, remember it exists only on this host — the
+operator's machine must fetch it first. Always emit this **step 0** before the push step
+(anonymous public fetch, no credentials needed):
+
+```
+  # 0. On a machine WITHOUT the branch pre-fetched, get it from the autonomic mirror:
+  cd <local checkout of the recipe>          # or: git clone https://git.autonomic.zone/recipe-maintainers/<recipe>.git
+  git remote add gitea https://git.autonomic.zone/recipe-maintainers/<recipe>.git 2>/dev/null || \
+    git remote set-url gitea https://git.autonomic.zone/recipe-maintainers/<recipe>.git
+  git fetch gitea +refs/pull/<PR_NUM>/head:refs/heads/<HEAD_REF>
+  git checkout <HEAD_REF>
+```
+
 In both modes the final output is a set of commands for the operator to run on a machine **with
 push access to `git.coopcloud.tech`** — always print them, even when everything local is
 already prepared.