From 5191f8b80d61e63d7ea34a7d31056ae131e08f6c Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
<41898282+github-actions[bot]@users.noreply.github.com>
Date: Sat, 21 Feb 2026 04:12:34 +0000
Subject: [PATCH 1/3] Use summary/details format for duplicate issue findings
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
.../gh-aw-duplicate-issue-detector.md | 146 ++++++++++++++++++
1 file changed, 146 insertions(+)
create mode 100644 github/workflows/gh-aw-duplicate-issue-detector.md
diff --git a/github/workflows/gh-aw-duplicate-issue-detector.md b/github/workflows/gh-aw-duplicate-issue-detector.md
new file mode 100644
index 00000000..6908d635
--- /dev/null
+++ b/github/workflows/gh-aw-duplicate-issue-detector.md
@@ -0,0 +1,146 @@
+---
+description: "Detect duplicate issues and notify reporters when a matching open or closed issue exists"
+imports:
+ - gh-aw-fragments/elastic-tools.md
+ - gh-aw-fragments/formatting.md
+ - gh-aw-fragments/rigor.md
+ - gh-aw-fragments/mcp-pagination.md
+ - gh-aw-fragments/messages-footer.md
+ - gh-aw-fragments/safe-output-add-comment.md
+engine:
+ id: copilot
+ model: gpt-5.3-codex
+ concurrency:
+ group: "gh-aw-copilot-duplicate-issue-detector-${{ github.event.issue.number }}"
+on:
+ workflow_call:
+ inputs:
+ additional-instructions:
+ description: "Repo-specific instructions appended to the agent prompt"
+ type: string
+ required: false
+ default: ""
+ allowed-bot-users:
+ description: "Allowlisted bot actor usernames (comma-separated)"
+ type: string
+ required: false
+ default: "github-actions[bot]"
+ detect-related-issues:
+ description: "Detect highly related (but not duplicate) issues in addition to exact duplicates (default: true)"
+ type: string
+ required: false
+ default: "true"
+ messages-footer:
+ description: "Footer appended to all agent comments and reviews"
+ type: string
+ required: false
+ default: ""
+ secrets:
+ COPILOT_GITHUB_TOKEN:
+ required: true
+ roles: [admin, maintainer, write]
+ bots:
+ - "${{ inputs.allowed-bot-users }}"
+concurrency:
+ group: duplicate-issue-detector-${{ github.event.issue.number }}
+ cancel-in-progress: true
+permissions:
+ contents: read
+ issues: read
+ pull-requests: read
+tools:
+ github:
+ toolsets: [repos, issues, pull_requests, search]
+strict: false
+timeout-minutes: 30
+safe-outputs:
+ noop:
+ report-as-issue: false
+ add-comment:
+ max: 1
+---
+
+# Duplicate Issue Detector
+
+Check whether newly opened issue #${{ github.event.issue.number }} in ${{ github.repository }} is a duplicate of, or highly related to, an existing open or previously closed/resolved issue. Do **not** triage or make an action plan — only determine whether a duplicate or highly related issue exists.
+
+## Context
+
+- **Repository**: ${{ github.repository }}
+- **Issue**: #${{ github.event.issue.number }} — ${{ github.event.issue.title }}
+
+## Process
+
+### Step 1: Understand the Issue
+
+Read the issue title and body carefully. Identify:
+- The core problem or request (in one sentence)
+- Key terms, error messages, component names, or identifiers you can use as search queries
+
+### Step 2: Search for Duplicates
+
+Run several targeted searches. Search **both open and closed** issues.
+
+Suggested queries (adapt based on the issue content):
+```
+repo:{owner}/{repo} is:issue "{key term from title}"
+repo:{owner}/{repo} is:issue is:closed "{key term from title}"
+repo:{owner}/{repo} is:issue "{error message or identifier}"
+```
+
+For each candidate result, read the title and (if promising) the body to assess similarity.
+
+### Step 3: Evaluate Candidates
+
+**Related issues detection setting**: ${{ inputs.detect-related-issues }}
+
+Classify each promising candidate using the categories below. If related issues detection is disabled (setting is `"false"`), only use the **Clear duplicate** and **Not related** categories — skip the **Highly related** category entirely.
+
+**Clear duplicate** — the candidate describes **the same underlying problem or request**:
+- Reports the same bug or requests the exact same feature
+- The affected component, behavior, and scope are the same
+- A fix for the candidate would fully resolve this issue too
+
+**Highly related** *(only when related issues detection is enabled)* — the candidate is closely related but **not** the same issue:
+- Covers a very similar area, component, or failure mode
+- One issue is a subset or superset of the other
+- Both issues overlap significantly but each has distinct scope or nuance
+
+**Not related** — skip it if:
+- The candidate only shares the same general topic area
+- The candidate is closed as "wont fix" or "invalid" with no resolution of the underlying issue
+- You are uncertain — when in doubt, err on the side of "not related"; if related issues detection is enabled, prefer "highly related" over "duplicate" for borderline overlapping cases
+
+### Step 4: Post Result
+
+Post **exactly one** `add_comment` call total (or `noop` if nothing is found). Do not call `add_comment` more than once.
+
+**If any duplicates (or highly related issues, when detection is enabled) were found:**
+
+Call `add_comment` with a single comment combining all findings. Include up to **3 duplicate issues** and, when related issues detection is enabled, up to **3 highly related issues**, each ranked from most to least relevant to the current issue. Use this format:
+
+```
+**Possible duplicates** (issues that appear to describe the same problem):
+- #{number}
+ {one concise sentence explaining why this issue overlaps with the candidate issue}
+ #{number}
+ {one concise sentence explaining why this issue overlaps with the candidate issue}
+ #{number}
+ {one concise sentence explaining the shared scope and the key difference from this issue}
+ #{number}
+ {one concise sentence explaining the shared scope and the key difference from this issue}
+ #{number}
+- #{number}: {candidate issue title}
{one concise sentence explaining why this issue overlaps with the candidate issue}
#{number}
+- #{number}: {candidate issue title}
{one concise sentence explaining why this issue overlaps with the candidate issue}
#{number}
+- #{number}: {candidate issue title}
{one concise sentence explaining the shared scope and the key difference from this issue}
#{number}
+- #{number}: {candidate issue title}
{one concise sentence explaining the shared scope and the key difference from this issue}
` because GitHub may not auto-expand `#{number}` references inside HTML summary tags. Use neutral, helpful language — the reporter may not be familiar with the existing issues. Do NOT use `fixes`, `closes`, or `resolves` keywords.
**If no duplicate (or highly related issue, when detection is enabled) is found:**
From f8b80bdb981541977d2c26d195441462548102db Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
<41898282+github-actions[bot]@users.noreply.github.com>
Date: Sat, 21 Feb 2026 04:34:31 +0000
Subject: [PATCH 3/3] Adjust duplicate issue output for badge visibility
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
.../gh-aw-duplicate-issue-detector.md | 22 +++++++++++--------
1 file changed, 13 insertions(+), 9 deletions(-)
diff --git a/github/workflows/gh-aw-duplicate-issue-detector.md b/github/workflows/gh-aw-duplicate-issue-detector.md
index 6a4b070a..49c29e7e 100644
--- a/github/workflows/gh-aw-duplicate-issue-detector.md
+++ b/github/workflows/gh-aw-duplicate-issue-detector.md
@@ -121,23 +121,27 @@ Call `add_comment` with a single comment combining all findings. Include up to *
```
**Possible duplicates** (issues that appear to describe the same problem):
-- #{number}: {candidate issue title}
- {one concise sentence explaining why this issue overlaps with the candidate issue}
+- #{number} — {one concise sentence explaining why this issue overlaps with the candidate issue}
+ More detail
+ {optional extra context about shared symptoms, component, or scope}
#{number}: {candidate issue title}
- {one concise sentence explaining why this issue overlaps with the candidate issue}
+- #{number} — {one concise sentence explaining why this issue overlaps with the candidate issue}
+ More detail
+ {optional extra context about shared symptoms, component, or scope}
#{number}: {candidate issue title}
- {one concise sentence explaining the shared scope and the key difference from this issue}
+- #{number} — {one concise sentence explaining the shared scope and the key difference from this issue}
+ More detail
+ {optional extra context about the overlap and distinction}
#{number}: {candidate issue title}
- {one concise sentence explaining the shared scope and the key difference from this issue}
+- #{number} — {one concise sentence explaining the shared scope and the key difference from this issue}
+ More detail
+ {optional extra context about the overlap and distinction}
` because GitHub may not auto-expand `#{number}` references inside HTML summary tags. Use neutral, helpful language — the reporter may not be familiar with the existing issues. Do NOT use `fixes`, `closes`, or `resolves` keywords.
+Omit the **Highly related** section entirely when related issues detection is disabled or when no issues qualify for it. Omit a section entirely if no issues qualify for it. Put issue references on the main list line (outside ``) so GitHub renders issue status badges. Keep `` text generic (for example, `More detail`) and avoid repeating issue titles there. In justifications, refer to the current report as **"this issue"** (not by number). Use neutral, helpful language — the reporter may not be familiar with the existing issues. Do NOT use `fixes`, `closes`, or `resolves` keywords.
**If no duplicate (or highly related issue, when detection is enabled) is found:**