Thanks again for bringing this up! We got to the bottom of this and we've got Triagster up and running in directus: github.com/directus/dir...
05.12.2024 15:50
👍 1
🔁 0
💬 0
📌 0
Thanks again for bringing this up! We got to the bottom of this and we've got Triagster up and running in directus: github.com/directus/dir...
Ah! Good catch!
Thanks Lars! GitHub uses purple checkmarks to indicate closed so I matched that here - but I do see how it's confusing. And I love the excerpt idea - added that to the backlog!
Funnily enough, I tried playing around with confidence scores earlier on - scores from vector embedding distances weren't very reflective of whether an issue was definitely a dupe or not and LLMs, by their nature, don't come up with very deterministic scores here. But something to keep looking into!
Just a heads up that the bot does not post comments on issues that existed before the bot is installed (Unless those issues are updated) - One of my goals for this bot was for it to be as quiet as possible and didn't want it to start commenting on 100s of issues on install. WDYT?
Thanks for the feedback! makes a lot of sense - Also working on making the bug body be user configurable! But for the time being, I've updated the default bug body to "Related Issues" as posted in this bot comment (Will update the screenshot assets next!): github.com/triagster/de...
a screenshot from triagster's report page for the Vite repository, showing a graph of the number of potential duplicate issues over time and below it, a table containing potential duplicate GitHub issues.
Excited to share triagster.com, an app that identifies potential duplicate GitHub Issues! This felt to me like the perfect use case for LLM backed semantic search. Would love for you try try it out and get your feedback 🙏
@vite.dev Here's the report for Vite: triagster.com/app/report/n... :)
@patak.dev Huge thanks again for sharing this! I’m the developer behind this app - please fire away any feedback or thoughts! Would love to hear them :)