fix: SublibraryCI fetch depth causes merge base failure on fork PRs#3159
Merged
ChrisRackauckas merged 1 commit intoSciML:masterfrom Mar 17, 2026
Merged
Conversation
The detect-changes job fails with "fatal: origin/master...HEAD: no merge base" on fork PRs because `git fetch origin master --depth=1` only retrieves a single commit of master history. This is insufficient for Git to compute the merge base needed by the three-dot diff. Remove the --depth=1 flag so the full base branch history is fetched, matching the fetch-depth: 0 already set on checkout. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude Opus 4.6 (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
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
detect-changesjob inSublibraryCI.ymlfails withfatal: origin/master...HEAD: no merge baseon PRs from forks (e.g. fix: DynamicQuantities compatibility in core + differentiation paths #3126)git fetch origin master --depth=1fetches only 1 commit of the base branch, which is insufficient for Git to compute the merge base needed by the three-dot diff (origin/master...HEAD)--depth=1so the full base branch history is fetched, consistent with thefetch-depth: 0already configured on the checkout stepTest plan
fatal: origin/master...HEAD: no merge baseat https://github.com/SciML/OrdinaryDiffEq.jl/actions/runs/23211895755/job/67492965893🤖 Generated with Claude Code