Detecting Duplicate Issues - Public Preview

[sunnyi101]

duplicate.detection.mp4

If you maintain a repo with more than a handful of issues, you know duplicates are a time sink. The same bug gets reported three different ways, you close the duplicate, link to the original, and repeat. For high-volume repos this adds up to hours of triage every week.

Duplicate detection is now available in public preview. When you're creating an issue, GitHub checks for potential duplicates as you type and surfaces them inline before you submit. No extra steps, no workflow changes. You see suggestions, you decide what to do with them.

How it works

As you fill out a new issue, once the title is complete and the body reaches 100 characters, we search for existing issues that look similar. If we find potential matches, up to three suggestions appear right in the issue form.

• Results are based on meaning, not just keyword matching
• Works in both the full-page and modal issue creation views
• Suggestions are non-blocking. You can always submit your issue regardless of what's shown

The goal is simple: catch duplicates at the point of creation, before they become triage work.

⏱️ When it triggers

Duplicate detection triggers when:

1. The issue title is filled out (at least 20 characters)
2. The issue body reaches 100 characters

We chose these thresholds to balance two things: giving enough signal to return good results, and showing suggestions early enough that you haven't already committed to submitting.

Once triggered, title edits will re-run the search. Body edits after the initial check won't re-trigger (to avoid distracting you while you're writing).

💬 Feedback

We're actively iterating on this and your input directly shapes what comes next. We'd love to hear:

1. Are the suggested duplicates relevant, or is it surfacing noise?
2. Does the timing feel right? Does it show up too early or too late in your writing flow?
3. Does the UI feel unobtrusive, or does it get in the way?

Share feedback, report issues, or suggest ideas in this discussion.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐