Duplicate issue detector workflow #197

Activity

1. elastic

   deleted a comment from github-actions on Feb 20, 2026
2. strawgate commented on Feb 20, 2026

   

   strawgate

   on Feb 20, 2026

   ContributorAuthor

   More actions

   /ai make a plan

   👀React with 👀1Reacted by github-actions
3. github-actions commented on Feb 20, 2026

   

   github-actionsBot

   on Feb 20, 2026 – with GitHub Actions

   Contributor

   More actions

   TL;DR: add a new lightweight duplicate-issue-detector workflow by cloning the issue-triage structure, narrowing the prompt to duplicate detection only, and wiring it into trigger/docs/smoke-test lists.

   Recommendation
   Create a dedicated GH Agent workflow that only checks whether a newly opened issue is a duplicate of open/closed prior issues, then posts one concise comment with links and confidence.

   Findings

   • Current triage already does duplicate-checking as part of a broader flow (.github/workflows/gh-aw-issue-triage.md:93-96) but also asks for full investigation/planning (.github/workflows/gh-aw-issue-triage.md:94-123).
   • Installable workflow shape is standardized: workflow shim in .github/workflows/gh-aw-(name).md, trigger example in gh-agent-workflows/(name)/example.yml, and docs in gh-agent-workflows/(name)/README.md (gh-agent-workflows/DEVELOPING.md:134-140).
   • Trigger files are copied via scripts/dogfood.sh (scripts/dogfood.sh:27-44), and install smoke tests use an explicit workflow allowlist (.github/workflows/smoke-test-install.yml:41-51).

   Verification
   No runtime commands/tests were needed for this planning-only response.

   Detailed Action Plan

   1. Add new shim .github/workflows/gh-aw-duplicate-issue-detector.md by copying .github/workflows/gh-aw-issue-triage.md and reducing scope:
      • Keep safeoutputs-add-comment only.
      • Keep GitHub issue/search tools.
      • Replace triage instructions with: gather issue context, search similar open/closed issues, score top matches, and conclude duplicate vs not duplicate vs uncertain.
   2. Add installable trigger gh-agent-workflows/duplicate-issue-detector/example.yml (based on gh-agent-workflows/issue-triage/example.yml) targeting gh-aw-duplicate-issue-detector.lock.yml@v0.
   3. Add gh-agent-workflows/duplicate-issue-detector/README.md with trigger, inputs, and safe-output docs (same format as gh-agent-workflows/issue-triage/README.md).
   4. Decide dogfooding behavior:
      • If enabled in this repo, ensure scripts/dogfood.sh does not exclude it.
      • If intentionally disabled, add it to EXCLUDED_WORKFLOWS with rationale.
   5. Update smoke install coverage in .github/workflows/smoke-test-install.yml by adding duplicate-issue-detector to WORKFLOWS if it should be validated by install/compile smoke tests.
   6. Run make compile and make lint-workflows to regenerate/check lockfiles and validate workflow syntax.
   7. Open PR with shim + lockfile + trigger + README + any list updates.

   Related Items

   Type	File	Relevance
   Existing workflow	.github/workflows/gh-aw-issue-triage.md:71-123	Closest baseline; already contains duplicate-check step but with broader triage scope
   Trigger template	gh-agent-workflows/issue-triage/example.yml:1-16	Canonical event/permissions/uses pattern
   Workflow authoring guide	gh-agent-workflows/DEVELOPING.md:134-140	Required files for adding a new installable workflow
   Trigger sync script	scripts/dogfood.sh:27-44	Controls copied trigger files in this repo
   Smoke install list	.github/workflows/smoke-test-install.yml:41-51	Determines install+compile coverage for workflows

   ---

   What is this? | From workflow: Issue Assistant

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #197
4. strawgate

   assigned

   Copilot

   and

   strawgate

   on Feb 20, 2026
5. strawgate

   closed this as completedin #199on Feb 20, 2026