refresh-data: rebase onto moved main before pushing the data commit - #30
Merged
Merged
Conversation
The 2026-09-01 refresh crawled for 77 minutes, committed 17 fresh data files — and lost it all when git push hit non-fast-forward because a workflow-kaizen merge landed on main mid-crawl. A long-running job must assume main moves under it: pull --rebase the single data commit onto current main before pushing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RicgHjbdeNb3ZGA6DMYMfS
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.
What
refresh-datanow runsgit pull --rebase origin mainimmediately before pushing its data commit.Why
The 2026-09-01 post-summer refresh crawled for 77 minutes, committed 17 fresh data files — and lost the whole crawl when
git pushhit non-fast-forward, because the #29 workflow-kaizen merge landed on main mid-crawl. A ~75-minute job must assume main moves under it; rebasing the single data-only commit is conflict-free by construction (the crawl touchespublic/data+ the linkcheck report only).Proof
YAML parses. The failure is verbatim in run 33557552467's log (
! [rejected] main -> main (fetch first)right after[main 018fb84] data: registry refresh (2026-09-01), 17 files changed). A fresh dispatch follows this merge — its push landing IS the proof.🤖 Generated with Claude Code
https://claude.ai/code/session_01RicgHjbdeNb3ZGA6DMYMfS
Generated by Claude Code