d32b8db635
* feat(#836): no-LLM duplicate-issue detection + challenge + 1-day auto-close Adds a deterministic (no-LLM) duplicate-issue governance lifecycle: - scripts/issue-dedupe.cjs: pure, unit-tested module (tokenize, Sørensen–Dice title similarity, scoreCandidates, renderChallengeComment, shouldClose) with fail-safe destructive-action guards. - duplicate-check.yml (issues:opened): scores new-issue title against open issues, posts a challenge comment + applies the pending `possible-duplicate` label on a clear match. - duplicate-sweep.yml (daily cron): closes possible-duplicate issues whose challenge comment is >24h old with no human reply and no 👎 veto; honors exempt labels; re-checks the label immediately before close (TOCTOU guard); strips the label on close to avoid reopen loops. - remove-duplicate-label.yml (issue_comment:created): clears the label and applies needs-maintainer-review when any human responds. - bug_report.yml / docs_issue.yml: add the required "I searched existing issues" preflight checkbox so all five forms force a pre-search attestation. - docs/agents/triage-labels.md: document the label + lifecycle. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore(#836): add changeset fragment for duplicate-issue detection Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
3.6 KiB
3.6 KiB
Triage Labels
Maps the five canonical triage roles to the actual label strings in open-gsd/gsd-core.
| Canonical role | Label in this repo | Notes |
|---|---|---|
needs-triage |
needs-triage |
Auto-applied by GitHub Action on every new issue |
needs-info |
needs-reproduction |
Waiting on reporter — cannot reproduce, more info required |
ready-for-agent |
confirmed |
Bug verified + fully specified — AFK agent can pick up |
ready-for-human |
approved-enhancement / approved-feature |
Enhancement/feature approved by maintainer — human codes it |
wontfix |
wontfix |
Will not be actioned |
possible-duplicate |
possible-duplicate |
Applied by the Duplicate check workflow when a new issue's title closely matches existing open issues. The reporter (or a maintainer) replies justifying why it is not a duplicate within 24h, or the Duplicate auto-close sweep closes it. A reply clears this label and applies needs-maintainer-review for human adjudication. React 👎 to the bot comment to veto auto-close. |
Notes on this repo's label model
confirmedis the AFK-agent-ready signal for bugs. It means "verified to exist and reproducible."- For enhancements and features, maintainer approval is
approved-enhancement/approved-featurerespectively. A contributor (human or agent) may not write code until one of these is applied. - There is no separate "ready-for-human" vs "ready-for-agent" distinction for enhancements — both flow through the same
approved-*labels. If the work requires human judgment (design decisions, external access), note it in the issue body. needs-triageis removed when any other state label is applied.needs-reproductionis used instead of the genericneeds-info— be specific in triage comments about what reproduction steps or information are missing.
Duplicate detection lifecycle
The possible-duplicate label is managed by three GitHub Actions workflows that together form a self-service deduplication loop:
- Detect on open — When an issue is opened,
duplicate-check.ymlscores its title against all other open issues using Dice-coefficient similarity. If any match clears the threshold, the bot posts a challenge comment listing the similar issues and appliespossible-duplicate. - Challenge comment + reporter window — The reporter (or a maintainer) has
DEFAULT_WINDOW_HOURS(24h) to reply explaining why the issue is not a duplicate. Reacting 👎 to the bot comment also signals the reporter objects to auto-close. - Daily sweep auto-close —
duplicate-sweep.ymlruns at 07:00 UTC daily. For each open issue withpossible-duplicate, it checks whether the window has elapsed, whether the reporter replied, and whether a 👎 reaction exists. Issues with exempt labels (priority: critical,pinned,confirmed-bug,confirmed,fix-pending) are never auto-closed. Issues that pass the close check receive a closing comment and are closed withstate_reason: duplicate. - Reporter reply clears label —
remove-duplicate-label.ymlfires on every new non-bot comment. If the issue still carriespossible-duplicate, it removes that label and appliesneeds-maintainer-review(the value ofHUMAN_REVIEW_LABELinscripts/issue-dedupe.cjs), routing the issue to a maintainer for manual adjudication.