Rule 15: Restore join ancestor check alongside Merge Interval#350
Merged
erikdarlingdata merged 1 commit intodevfrom Feb 27, 2026
Merged
Rule 15: Restore join ancestor check alongside Merge Interval#350erikdarlingdata merged 1 commit intodevfrom
erikdarlingdata merged 1 commit intodevfrom
Conversation
Merge Interval + TopN Sort is the strongest signal for OR expansion, but the join ancestor check is a broader catch that shouldn't have been removed. Now fires on either condition. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
HasJoinAncestorcheck that was incorrectly removed in PR Rule 15: Use Merge Interval for OR expansion detection #349Test plan
dotnet buildclean (0 errors) for Dashboard and Lite🤖 Generated with Claude Code