Repository navigation
Avoid cross-repository PR shorthand misattribution - #148
Merged
Merged
Conversation
laclance
marked this pull request as ready for review
October 7, 2026 15:50
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
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
Fix the spurious production lookup seen in private run #13:
Nakagawa-master/nakagawa-theory-archive PR #13406The source comment explicitly identifies Qwen's external PR:
https://github.com/QwenLM/qwen-code/pull/13406but also repeats
implementation PR #13406. The scanner treated that shorthand as if it belonged to the issue repository and attempted a bogus same-repository PR lookup.This keeps the existing same-repository shorthand mechanism, but ignores a shorthand when a nearby fully-qualified PR URL with the same number clearly points to a different repository.
Regression coverage
PR #13406echo does not trigger a same-repo lookupScope
Only:
opportunity_scout/strategic/competition.pytests/strategic/test_competition.pyNo readiness, scoring, private-instance, or release changes.