fix(ci): establish baseline before content check to prevent false positives#18
Merged
sonupreetam merged 1 commit intoMay 21, 2026
Conversation
…itives 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 complytime#17 Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
writeFileSafehad no baseline to compare against on a fresh CI runner (content/docs/projects/*/is gitignored).--writestep using the committed lock SHAs to populate the runner's disk before--update-lockand the actual content check, sowriteFileSafecan detect only genuine content differences.Evidence: PR #15 and PR #16 list the identical 32 files across the same 5 repos — only pinned SHAs differ.
Fixes #17
Test plan
workflow_dispatch) or wait for next weekly cronhas_changes=false)Made with Cursor