Repository navigation
Recognize active putting-up-PR claims - #155
Merged
Merged
Conversation
laclance
marked this pull request as ready for review
October 8, 2026 18:17
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 a production competition-detection gap exposed after the historical-PR attribution fix.
In
grpc/grpc-go#9470, a contributor wrote before private run #13:That is explicit active implementation ownership, but the strategic claim parser recognizes nearby forms such as “I'll open a PR” and “I'm implementing” while missing “Putting up a PR”.
This change adds that narrow active-claim phrase family.
Safety boundary
Putting up a PR:orPutting up a PR to ...countPutting up a PR would help ...does not countRegression coverage
Putting up a PR: ...is recognizedScope
Only:
opportunity_scout/strategic/claims.pytests/strategic/test_claims.pyThis intentionally does not touch draft PR #154's shared-tracker competition logic.