Skip to content

Conversation

christian-schilling
Copy link
Member

The default history simplification will not drop merge commits if their tree differs from any parent.
In most cases however merges that don't differ from the first parent are not wanted in the output history.
This new filter allows to prune them.

Change: prune-trivial-merges

@christian-schilling christian-schilling force-pushed the @changes/master/christian.schilling.de@gmail.com/prune-trivial-merges branch 3 times, most recently from 6cdcb13 to 5d320f5 Compare September 25, 2025 15:58
The default history simplification will not drop merge
commits if their tree differs from any parent.
In most cases however merges that don't differ from the first
parent are not wanted in the output history.
This new filter allows to prune them.

Change: prune-trivial-merges
@christian-schilling christian-schilling force-pushed the @changes/master/christian.schilling.de@gmail.com/prune-trivial-merges branch from 5d320f5 to df1a10a Compare October 9, 2025 21:29
@christian-schilling christian-schilling marked this pull request as ready for review October 9, 2025 21:29
@christian-schilling christian-schilling added this pull request to the merge queue Oct 9, 2025
Merged via the queue into master with commit 68709d4 Oct 9, 2025
1 check passed
@christian-schilling christian-schilling deleted the @changes/master/christian.schilling.de@gmail.com/prune-trivial-merges branch October 9, 2025 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants