-
Notifications
You must be signed in to change notification settings - Fork 66
Triage tool deals with non-linear history #1538
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
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
Steboss
commented
Jul 9, 2025
Steboss
commented
Jul 9, 2025
Steboss
commented
Jul 9, 2025
Steboss
commented
Jul 9, 2025
Steboss
commented
Jul 9, 2025
Steboss
commented
Jul 9, 2025
Steboss
commented
Jul 9, 2025
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
…ox into sbosisio/triage_history
Contributor
Author
|
@olupton |
olupton
reviewed
Jul 15, 2025
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
Co-authored-by: Olli Lupton <[email protected]>
…ox into sbosisio/triage_history
Contributor
Author
|
@olupton |
olupton
approved these changes
Jul 15, 2025
Collaborator
olupton
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
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.
If commits do not lie on the same linear git history. The tool would use
git fetchbecause it couldn't find a direct path between the passing and failing commits.Here the changes introduce a new logic to find the correct bisection range:
git merge-baseto identify common ancestors between the passing and failing commit