Use node degree in bisect mode - #31
Open
Mshehu5 wants to merge 1 commit into
Open
Conversation
Within each midpoint level, prioritize commits with many parents or children. This surfaces informative graph junctions earlier when narrowing down the origin of failures.
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.
Improve
validate-commits --bisectordering by considering commit-graph node degree.Within each midpoint level commits are prioritized by the number of in-range parents and children they have. This surfaces informative graph points earlier, including merge commits with many parents, base commits with many children and commits with both many parents and many children.
Tesed
bisectagainst the high-arity commit graph on develop branch.