ci: force-update the base ref in change detection - #6463
Merged
Merged
Conversation
Change detection on #6417 failed with `! [rejected] main -> origin/main (non-fast-forward)`: main moved (the #6431 merge) after checkout had fetched origin/main, and the --depth=1 fetch cannot prove the new tip descends from the old one. The ref is a scratch remote-tracking ref for the diff base, so a forced update is always right. Verification: actionlint with CI's flags clean. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.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
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.
Refs #6458
Change detection on #6417 failed with
! [rejected] main -> origin/main (non-fast-forward). The sequence:origin/main.mainthen moved, when fix(fleet): publish without a two-link window on Linux and macOS #6431 merged.--depth=1base fetch couldn't prove the new tip descends from the old one, so git refused the update.The ref is only a scratch diff base, so a forced update (
+refspec) is always correct.Verification: actionlint with CI's flags is clean.
🤖 Generated with Claude Code