Skip to content

Conversation

@Steboss
Copy link
Contributor

@Steboss Steboss commented Jul 3, 2025

If commits do not lie on the same linear git history. The tool would use git fetch because 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:

  • apply git merge-base to identify common ancestors between the passing and failing commit
  • at build-and-run stage we're checking out the base commit from the main branch, and we apply cherry-pick for all new relevant features

@Steboss Steboss marked this pull request as draft July 4, 2025 11:35
@Steboss Steboss requested a review from olupton July 15, 2025 10:57
@Steboss
Copy link
Contributor Author

Steboss commented Jul 15, 2025

@olupton
re-ready for review
thank you 🙏

@Steboss
Copy link
Contributor Author

Steboss commented Jul 15, 2025

@olupton
re-re-ready for a new review

Copy link
Collaborator

@olupton olupton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@Steboss Steboss merged commit e5a1f2e into main Jul 15, 2025
4 checks passed
@Steboss Steboss deleted the sbosisio/triage_history branch July 15, 2025 15:54
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