fix(ci): stop storage-compat.sh from shallowing a full clone

The baseline fetch passed --depth=1 unconditionally. On the CI
checkout that is a no-op, but on a developer's full clone git does
not skip anything: it writes the fetched tip into .git/shallow and
grafts every older commit off the history, for every worktree that
shares the repository. A local run left master cut at its tip and
git status counting the whole old history as remote-only commits.

Pass --depth=1 only when the repository is already shallow.

Author: hubcio

scripts/ci/storage-compat.sh

@@ -139,8 +139,17 @@ fi
 
 # The remote side of a fetch takes a branch or tag name (or a reachable SHA),
 # never a remote-tracking name, so drop the remote prefix before asking origin.
+#
+# --depth=1 only where the clone is already shallow (the CI checkout). On a
+# full clone that flag does not save anything, it WRITES a shallow boundary at
+# the fetched tip and grafts every older commit off the developer's history,
+# for every worktree sharing the repository.
+FETCH_DEPTH=()
+if [ "$(git rev-parse --is-shallow-repository)" = "true" ]; then
+  FETCH_DEPTH=(--depth=1)
+fi
 FETCHED=0
-if git fetch --no-tags --depth=1 origin "${BASELINE_REF#origin/}" 2>/dev/null; then
+if git fetch --no-tags "${FETCH_DEPTH[@]}" origin "${BASELINE_REF#origin/}" 2>/dev/null; then
   FETCHED=1
 fi