fix(ci): monitor publish step fails once the data branch exists#24
Merged
Conversation
The last two scheduled sweeps ran to completion but threw away their results at the commit step: 'git checkout -B registry-snapshots origin/registry-snapshots' aborts with 'untracked working tree files would be overwritten by checkout' because the freshly generated latest.json / snapshot-*.json sit untracked in data/registry-snapshots/ and collide with the branch's tracked versions. The first run escaped this (orphan-branch path, no existing branch to collide with). Fix: after copying the fresh files to $tmp, rm -rf data/registry-snapshots before the checkout so nothing blocks the switch, then overlay them back. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DNoTXU8k3pfSBzR7aJubqL
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.
Description
The last two scheduled sweeps (runs #8, #9) ran the full scan + escalation successfully but failed at the commit step — so their results were thrown away. That's why chunk 2 never landed on
registry-snapshots.Cause:
git checkout -B registry-snapshots origin/registry-snapshotsaborts with "untracked working tree files would be overwritten by checkout" — the freshly generatedlatest.json/snapshot-*.jsonsit untracked indata/registry-snapshots/and collide with the branch's tracked versions. The first run escaped this because the branch didn't exist yet (orphan-branch path, nothing to collide with), so the bug only shows up from the second run onward.Fix: after copying the fresh files to
$tmp,rm -rf data/registry-snapshotsbefore the checkout so nothing blocks the switch, then overlay them back.Type of Change
Checklist
🤖 Generated with Claude Code
https://claude.ai/code/session_01DNoTXU8k3pfSBzR7aJubqL
Generated by Claude Code