Add support for merging unrelated Git histories - #119
Open
IngoMeyer441 wants to merge 1 commit into
Open
Conversation
When merging unrelated Git histories, the merge driver uses an empty ancestor database. Thus, the SQL `max` function cannot operate and returns a `null` value during the merge, effectively discarding *our* database during the merge. This commit ignores the ancestor database if it is empty, so both histories are full preserved in this corner case.
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
1 participant
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.
When merging unrelated Git histories, the merge driver uses an empty
ancestor database. Thus, the SQL
maxfunction cannot operate andreturns a
nullvalue during the merge, effectively discarding ourdatabase during the merge. This PR ignores the ancestor database if
it is empty, so both histories are fully preserved in this corner case.