You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found during the 2026-07-06 incident audit (parent: #1667), and directly related to the user's stated goal of contributors being "credited properly" and duplicate work being "handled gracefully."
Today, when a losing sibling in a duplicate cluster is gate-blocked/auto-closed (via isDuplicateClusterWinnerByClaim, see #(true-creation-time fix issue)), the close comment explains that another open PR already links the same issue, but does not name or link which specific PR won, so the closed contributor has to go hunt for it themselves (and has no way to easily verify their work wasn't simply lost/ignored).
Ensure the winner's PR number is threaded through to wherever the close-reason/comment text is composed (the winner is already computed via isDuplicateClusterWinnerByClaim/openSiblingsForPr for gating purposes — this only requires surfacing which specific sibling number was the elected winner instead of just a boolean).
Add a test asserting the close comment for a losing PR contains the winning PR's number/link.
Deliverables
Wherever the duplicate-cluster close reason/comment is composed (near the processors.ts:7275 call site and its close-comment templating): include the winner's PR number/link.
Regression test asserting the generated close comment names the correct winning PR number.
Expected outcome
A contributor whose PR is closed as a duplicate immediately sees which specific PR won and can go verify their own contribution wasn't silently discarded, instead of just being told "another PR already exists" with no pointer to it.
Context
Found during the 2026-07-06 incident audit (parent: #1667), and directly related to the user's stated goal of contributors being "credited properly" and duplicate work being "handled gracefully."
Today, when a losing sibling in a duplicate cluster is gate-blocked/auto-closed (via
isDuplicateClusterWinnerByClaim, see #(true-creation-time fix issue)), the close comment explains that another open PR already links the same issue, but does not name or link which specific PR won, so the closed contributor has to go hunt for it themselves (and has no way to easily verify their work wasn't simply lost/ignored).Requirements
isDuplicateClusterWinnerByClaim/openSiblingsForPrfor gating purposes — this only requires surfacing which specific sibling number was the elected winner instead of just a boolean).Deliverables
processors.ts:7275call site and its close-comment templating): include the winner's PR number/link.Expected outcome
A contributor whose PR is closed as a duplicate immediately sees which specific PR won and can go verify their own contribution wasn't silently discarded, instead of just being told "another PR already exists" with no pointer to it.