add NO_DEEP_MERGE_HISTORY env - to allow only history-merges up to 2-steps#19553
Merged
AskAlexSharov merged 1 commit intomainfrom Mar 2, 2026
Merged
add NO_DEEP_MERGE_HISTORY env - to allow only history-merges up to 2-steps#19553AskAlexSharov merged 1 commit intomainfrom
NO_DEEP_MERGE_HISTORY env - to allow only history-merges up to 2-steps#19553AskAlexSharov merged 1 commit intomainfrom
Conversation
Giulio2002
approved these changes
Mar 2, 2026
Collaborator
Giulio2002
left a comment
Giulio2002
left a comment
There was a problem hiding this comment.
LGTM — simple env var addition for NO_DEEP_MERGE_HISTORY with a clean 3-line guard in findMergeRange
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.
fast merges, less impact on exec, less disk space (10x for comm history)