From cda023088f3b727f378fdac30effce603fa4d7c4 Mon Sep 17 00:00:00 2001 From: Coco Sheng Date: Thu, 9 Apr 2026 13:50:12 -0400 Subject: [PATCH] docs(triage): explicitly check for newer duplicates with active PRs --- .gemini/skills/github-issue-triage/references/triage_rules.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.gemini/skills/github-issue-triage/references/triage_rules.md b/.gemini/skills/github-issue-triage/references/triage_rules.md index 6de0143470..a019074001 100644 --- a/.gemini/skills/github-issue-triage/references/triage_rules.md +++ b/.gemini/skills/github-issue-triage/references/triage_rules.md @@ -137,7 +137,8 @@ Is the issue fundamentally missing context AND no one has asked for more informa - If still valid: Proceed to Step 5. ## Step 5: Duplicates -Search for duplicates using `gh issue list --search "" --repo --state all`. +Search for duplicates using `gh issue list --search "" --repo --state all`. +- **CRITICAL**: Pay special attention to newer issues that might already have active pull requests or more detailed context. If a duplicate exists that already has an active PR or more maintainer engagement, close the *current* issue you are triaging in favor of the active one. - If found: `gh issue close --reason "not planned" --comment "Closing as duplicate of #."` and **STOP EXECUTION**. - If no duplicates: Proceed to Step 6.