From c78c237dc772258612c9d50e4138f0488737dfd0 Mon Sep 17 00:00:00 2001 From: weichen Date: Tue, 13 Oct 2026 04:14:03 +0000 Subject: [PATCH] Fetch pinned RDM history deep enough for ancestry Why: depth 1 makes prev_sha and sha unrelated shallow roots, so update reports a fork instead of an upgrade. Evidence: SELF the pin-fetch credential test; CI run 2829 showed the fork message. Impact: test-pg fetches 200 commits from each pin, not the full history. Refs: .task/feature-svc-d3-real-scenarios.md Co-authored-by: Cursor --- .gitea/workflows/ci.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/ci.yaml b/.gitea/workflows/ci.yaml index f3a07667..8970e45b 100644 --- a/.gitea/workflows/ci.yaml +++ b/.gitea/workflows/ci.yaml @@ -421,7 +421,9 @@ jobs: PY ) [ "${#pins[@]}" -eq 3 ] - git -C rdm fetch --depth=1 origin "${pins[@]}" + # depth=1 会把三个 pin 变成互不相关的浅根，update 会把 prev→sha 误判成分叉。 + # 当前 first-parent 距离是 39，200 留余量，仍不拉全史。 + git -C rdm fetch --depth=200 origin "${pins[@]}" for rev in "${pins[@]}"; do git -C rdm checkout --detach "$rev" git -C rdm submodule update --init --recursive