initialize-semantic-issue-similarity-analysis-and-duplicate-detection-automation-workflow

[aniket866]

🚀 The feature

Problem: Before opening a new issue, people have to manually check many old issues. This takes time and still causes duplicate issues.

Fix and How: Use a GitHub bot and a simple GitHub Action to automatically check new issues and show similar existing ones.

Impact: Duplicate issues get clearly marked, so maintainers don’t have to spend extra time checking or replying again.

Notes: The system will only suggest duplicates and will not auto-close any issue.

Motivation, pitch

Why: This reduces duplicate issues, saves maintainer time, and helps contributors quickly find existing discussions without strict manual scanning.

@SharkyBytes Please review and can be merged , please let me know if any issue

[coderabbitai]

Warning

Rate limit exceeded

@aniket866 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 4 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[SharkyBytes]

have you tested this action on the actual repo (fork/staging) and did it detect duplicates accurately without false positives, and how long did it take to run? Also, roughly how many issues the repo currently has....if it’s large (e.g., 1000+), we may need optimizations like limiting to open issues or caching to avoid timeouts. and also do GitHub Actions has issues: write permission and whether the duplicate label already exists or needs to be created. Additionally, is the 82% similarity threshold finalized or will it be monitored/tuned based on usage? Does this close or link to an existing issue/feature request? Finally, how are edge cases handled (empty/very short issues, rate limits), and who will maintain/monitor it for false positives or model updates going forward?

[SharkyBytes]

Please attach the POW for the same

[aniket866]

Please attach the POW for the same

HI @SharkyBytes
I have done all testing it is working good

aniket866/PictoPy#5 check for more details

testing:

in my fork I created a issue , and this issue is compared with original repo of your(pictopy) and marked duplicate

it take 2-3 minutes to analyze since it uses github bot , as coderabbit takes 2-3 minutes so same time it also takes

here is the video, it is long so keep forwarding and check the result at the end
https://drive.google.com/file/d/1U3W-LWR_GCP4m1vgpbMDCZFlGSh_WgTt/view?usp=sharing