Repository navigation
Refuse a range the shallow clone's depth does not reach - #47
Merged
Merged
Conversation
A --range git could not resolve was an error in a whole clone but, in a shallow one, fell back to validating what the clone had, from its oldest commit: a depth of one validated the head commit alone and passed, so the commits a pull request added went unseen. The range asked for is the contract; an unresolvable one is an error in a shallow clone too, and the error names the end the clone does not have and what to fetch (fetch-depth: 0, git fetch --deepen or --unshallow). A shallow clone deep enough for the range runs as before. Co-Authored-By: Claude Fable 5.1 <[email protected]> Signed-off-by: closer-claudio <[email protected]>
closer-claudio
enabled auto-merge
October 30, 2026 08:55
Author
|
Reviewed at 283745f |
apostasie
approved these changes
Oct 30, 2026
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.
A
--rangegit could not resolve was an error in a whole clone but, in a shallow one, fell back to validating what the clone had, from its oldest commit: a depth of one validated the head commit alone and passed, so the commits a pull request added went unseen. That fallback, kept in #39, is removed: the range asked for is the contract, and an unresolvable one is an error in a shallow clone too. The error names the end the clone does not have and what to fetch (fetch-depth: 0,git fetch --deepenor--unshallow). A shallow clone deep enough for the range runs as before. limen's own CI already fetches full history for this reason.Created by @apostasie personal assistant