From 4db4c171901ffbbde1767e6282d5587f7e9df6a9 Mon Sep 17 00:00:00 2001 From: Molecule AI Core-BE Date: Mon, 11 May 2026 09:21:49 +0000 Subject: [PATCH] fix(ci): add fetch-depth:0 to detect-changes checkout (harness-replays) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The detect-changes job's git diff on base.sha was silently returning empty because the default fetch-depth:1 only fetches the PR head commit — the base ref is absent from local history. This caused harness-replays to report "Failing after 10-18s" on ALL PRs regardless of whether relevant files changed. Fixes issue #441. Co-Authored-By: Claude Opus 4.7 --- .gitea/workflows/harness-replays.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.gitea/workflows/harness-replays.yml b/.gitea/workflows/harness-replays.yml index 9186f673..694d167e 100644 --- a/.gitea/workflows/harness-replays.yml +++ b/.gitea/workflows/harness-replays.yml @@ -68,6 +68,14 @@ jobs: run: ${{ steps.decide.outputs.run }} steps: - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2 + with: + # fetch-depth: 0 is required so the base.sha (PR merge-base) is + # present for the git diff in the next step. Without it, the default + # fetch-depth: 1 only fetches the PR head commit; the base ref is + # absent and git diff silently returns empty, causing the detect-changes + # step to report no relevant changes even on files that ARE relevant. + # Verified 2026-05-11 against harness-replays run failures. + fetch-depth: 0 - id: decide run: | # workflow_dispatch: always run (manual trigger) -- 2.45.2