Feature Request: AI-Powered Issue Deduplication and Pre-Submission Triage #189316
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Feature Area
Issues
Body
GitHub would benefit greatly from adding AI-powered issue triage before submission, not only after an issue has already been created.
In many active repositories, maintainers spend a large amount of time dealing with duplicate issues, incomplete bug reports, unclear categories, and repetitive support questions. This creates unnecessary noise and slows down real development work.
A more helpful workflow would be:
While a user is typing an issue title and description, GitHub should show similar existing issues, discussions, pull requests, and related documentation in real time.
Before submission, GitHub should suggest a category such as:
If an issue appears to be a likely duplicate, GitHub should warn the user and let them decide whether to continue or join the existing thread.
GitHub should also detect missing information such as version, platform, reproduction steps, logs, screenshots, or environment details before submission.
This kind of AI assistance would be more valuable than many code-generation features, because issue and PR triage is repetitive, high-volume, and expensive for maintainers. It would improve repository quality, reduce duplicate reports, and make collaboration more efficient for both users and project owners.
In short, AI should help keep repositories organized at the source, instead of only helping clean up the mess afterward.
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions