[FEATURE]: Detect Potential Duplicate Issues and PRs on Governance Page

未关闭
#386 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@amankv1234 已经在做这个了。

开始于 2026年10月29日。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
66/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github, javascript, react

调研方向

Start by reading src/pages/GovernancePage.jsx and how it receives issuesData from AppContext.jsx; then inspect the existing governance tabs and their tests. The issue proposes a pure similarity service in src/services/duplicateDetection.js with tests in src/services/duplicateDetection.test.js. Done means the new tab lists likely duplicate open issues and PRs with the requested filters, scores, repository names, and GitHub links, without extra API calls.

由索引模型根据 Issue 内容生成。

描述

enhancement
Feature and its Use Cases
Summary

Add a new check/tab on the Governance Page (/governance) to detect and list Potential Duplicate Issues and PRs across repositories.

Problem Statement

In open-source organizations, multiple contributors often open duplicate bug reports or identical pull requests without realizing that a similar issue or PR is already open. Maintainers currently have to search and identify these duplicates manually.

Proposed Solution

Add a "Duplicate Issues & PRs" tab to the Governance page that runs 100% client-side over already-fetched repository data:

  1. Title & Text Similarity:
    • Evaluates open issues against open issues, and open PRs against open PRs within each repository.
    • Uses a deterministic, lightweight client-side Jaccard similarity index ($J(A, B) \ge 0.75$) on cleaned and tokenized titles.
  2. Governance UI Integration:
    • Add a 5th tab alongside Dead Issues, Zombie PRs, Stale Issues Ratio, and No License.
    • Filter chips to switch between: All, Issues, and PRs.
    • Table displaying: Original Item, Potential Duplicate, Repository, Similarity Score, and direct GitHub links.
User & Maintainer Benefits
  • Helps maintainers spot and clean up duplicate issues/PRs quickly.
  • Prevents redundant efforts and keeps repository backlogs clean.
Additional Context
🛡️ API Rate-Limit & Performance
  • Zero Extra API Calls: Uses 0 extra GitHub API requests. It purely derives insights from issuesData already fetched by auditRepos() in AppContext.jsx (which is already cached for 1 hour in IndexedDB).
  • Mode Scoping Parity: Fully respects Standard Mode (top 10 repos per org, 1 page) and Complete Mode (all repos, 10 pages).
  • Client Performance: Comparisons are isolated per repository (<100 items), completing in < 15ms inside useMemo without blocking the main UI thread.
Implementation Plan
  1. Add src/services/duplicateDetection.js with pure title similarity algorithms.
  2. Add unit tests in src/services/duplicateDetection.test.js to verify edge cases and thresholds.
  3. Add the tab and table view to src/pages/GovernancePage.jsx.
Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
主要语言
JavaScript
星标
53
派生
182
平均合并
18 分钟
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AOSSIE-Org/OrgExplorer 的其他 Issue

查看 AOSSIE-Org/OrgExplorer 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。