fix: improve commit range resolution logic in git.go #55
Conversation
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
dexyk
force-pushed
the
dk/fix_git_diff
branch
3 times, most recently
from
3054dcd to
4f2e7fd
Compare
… more reliable merge base detection
dexyk
force-pushed
the
dk/fix_git_diff
branch
from
4f2e7fd to
8ac3085
Compare
hamir-suspect
approved these changes
Oct 29, 2025
Merged
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.
Ensure
change_inignores empty merge commits in shallow clones. Guard the unshallow logic so three-dot ranges wait for a real merge base. Once available, continue with the diff.