Skip to content

fix(duplicate-issue-detector): improve comment formatting for related vs duplicate issues #340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
strawgate merged 4 commits into from
Feb 21, 2026
Merged

fix(duplicate-issue-detector): improve comment formatting for related vs duplicate issues #340

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7ac1333
Initial plan
Copilot Feb 21, 2026
cf0c5e9
Fix duplicate issue detector formatting: collapse related issues, kee…
Copilot Feb 21, 2026
dcf57ad
Simplify Step 4 instructions: two concrete examples, no nested detail…
Copilot Feb 21, 2026
8a2dc94
update prompt
strawgate Feb 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions .github/workflows/gh-aw-duplicate-issue-detector.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 5 additions & 1 deletion .github/workflows/gh-aw-duplicate-issue-detector.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,6 +136,8 @@ Call `add_comment` with a single comment combining all findings. Include up to *
{optional extra context about shared symptoms, component, or scope}
</details>

<details><summary>{N} related issues found</summary>

**Highly related** (separate issues that significantly overlap or share scope):
- #{number} — {one concise sentence explaining the shared scope and the key difference from this issue}
<details><summary>More detail</summary>
Expand All @@ -145,9 +147,11 @@ Call `add_comment` with a single comment combining all findings. Include up to *
<details><summary>More detail</summary>
{optional extra context about the overlap and distinction}
</details>

</details>
```

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 `<summary>`) so GitHub renders issue status badges. Keep `<summary>` 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.
Omit the **Possible duplicates** section entirely if no issues qualify for it. Omit the `<details>` block wrapping **Highly related** entirely when related issues detection is disabled or when no issues qualify for it. Put issue references on the main list line (outside any `<summary>`) so GitHub renders issue status badges. Keep `<summary>` text generic (e.g. `More detail` or `{N} related issues found`) and do NOT repeat issue titles or numbers anywhere inside `<details>` bodies. In justifications, refer to the current report as **"this issue"** (not by number) and refer to the candidate by "it" or a short description — never by repeating the title or issue 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:**

Expand Down
Loading