ref(grouping): Include Seer distance in merged issues response#117965
Merged
lobsterkatie merged 3 commits intoJun 18, 2026
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
lobsterkatie
force-pushed
the
kmclb-include-seer-match-distance-in-merged-issues-response
branch
from
3d90207 to
ef23aa2
Compare
yuvmen
reviewed
Jun 17, 2026
yuvmen
left a comment
yuvmen
left a comment
Member
There was a problem hiding this comment.
yea this looks correct, waiting on approve cuz its red, will approve once its all ironed out and not in draft
lobsterkatie
force-pushed
the
kmclb-include-seer-match-distance-in-merged-issues-response
branch
from
ef23aa2 to
ef98f35
Compare
lobsterkatie
force-pushed
the
kmclb-include-seer-match-distance-in-merged-issues-response
branch
from
ef98f35 to
fc0587b
Compare
cvxluo
approved these changes
Jun 18, 2026
lobsterkatie
deleted the
kmclb-include-seer-match-distance-in-merged-issues-response
branch
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
3 participants
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.
For debugging purposes, it would be helpful to know how closely a hash matched to another when they're merged by Seer. This updates the API response to include this information, and the corresponding test to check for it. (I also simplified the test quite a bit, since I was already editing it.)