From 5139fd800a9b50a2bc59268903980da5ae1f6b79 Mon Sep 17 00:00:00 2001 From: sonupreetam Date: Wed, 20 May 2026 13:31:28 +0200 Subject: [PATCH] fix(ci): establish baseline before content check to prevent false positives The sync workflow always reported all files as changed because writeFileSafe had no baseline to compare against on a fresh runner. Add a preliminary --write step with the current (committed) lock SHAs so the subsequent check step can detect only genuine content changes. Fixes #17 Co-authored-by: Cursor --- .github/workflows/sync-content-check.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/sync-content-check.yml b/.github/workflows/sync-content-check.yml index 79b15eb..8ff6391 100644 --- a/.github/workflows/sync-content-check.yml +++ b/.github/workflows/sync-content-check.yml @@ -23,6 +23,11 @@ jobs: with: go-version-file: go.mod + - name: Sync content at current lock SHAs + run: go run ./cmd/sync-content --org complytime --config sync-config.yaml --lock .content-lock.json --write + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + - name: Update content lock run: go run ./cmd/sync-content --org complytime --config sync-config.yaml --lock .content-lock.json --update-lock env: