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

オープン
#386 コメント 2 件 リアクション 0 件 担当者 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分
マージ済み PR(30日)
2

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

AOSSIE-Org/OrgExplorer のほかの issue

AOSSIE-Org/OrgExplorer の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。