Maintainers spend hours every week closing duplicate issues. 😮‍💨 That changes with duplicate detection. Surface up to 3 matching issues as you create one, before you hit submit.

Jul 1, 2026 · 5:13 PM UTC

21
23
217
62,566
Now in public preview 👇 github.blog/changelog/2026-0…
6
3
20
12,037
Sort replies: Relevant Recent Liked
Replying to @github
humans saw the same bug, filed it 12 times, and called it community engagement
149
Replying to @github
How about just banning AI slop...
49
Replying to @github
Then what change
1
41
Replying to @github
Great feature! This should significantly cut down on maintainer burnout. Any plans to make the similarity threshold adjustable or add it to the API for custom workflows?
1
201
Replying to @github
This is a really cool feature. Kudos!
1
66
Replying to @github
Wait Kali Linux buiit GitHub Is he also the one managing this account ?🤔
1
61
Replying to @github
The best features save time you didn’t know you were losing.
1
117
Replying to @github
Fable 5 please :D
66
Replying to @github
An AI agent to manage your security and infrastructure? Yes, we already have one. This is V2, and it is a different machine. Smarter reasoning, faster responses, a cleaner interface, and it now costs 80% less to run.
176
Replying to @github
Works until people just type "bug" and hit submit anyway 🤷
201
Replying to @github
Can't wait for users to ignore 3 matching issues and hit submit anyway. 🤷
120
Replying to @github
Works for regular bugs, but the good duplicates always use completely different words 🤷
239
Replying to @github
Now they can ignore three matching issues instead of zero 🤷
71
Replying to @github
Works until someone describes the exact same bug in three completely different ways 🤷
274
Replying to @github
Catching duplicates before submit is probably the least annoying way to keep a repo clean.
48
Replying to @github
这个功能早该有了,维护者真的会少很多重复劳动
50
Replying to @github
Duplicate issue detection before submit is the kind of developer workflow improvement that seems small but saves thousands of hours across the ecosystem. The real test is whether it catches semantic duplicates where the wording is different but the underlying bug is the same.
92