Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub introduces sub-issues, issue types and advanced search

github.blog

Post reply on HN
Print view View original

81–90 of 213 posts

Re: GitHub introduces sub-issues, issue types and advanced search

#81

Post by alexpovel »

hamandcheese wrote: post #48

A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.

Agree!

For fun, I had put together a GitHub bot for this purpose a while ago. It indexes all existing issues in a repo, creates embeddings and stores them in a vector DB. When a new issue is created, the bot comments with the 3 most similar, existing issues, from vector similarity.

In theory, that empowers users to close their own issues without maintainer intervention, provided an existing & solved issue covers their use case. In practice, the project never made it past PoC.

The mechanism works okay, but I've found available (cheap) embedding models to not be powerful enough. For GitHub, technology-wise, it should be easy to implement though.

https://github.com/alexpovel/issuedigger

Re: GitHub introduces sub-issues, issue types and advanced search

#82

Post by trollbridge »

idunnoman1222 wrote: post #57
weinzierl wrote: post #46

Earlier quoted context omitted.

If you search code for a string you know is there it is completely git or miss if it is found. Always has been like that. Also see https://news.ycombinator.com/item?id=35144250

Oh yeah, where on the Internet does this work reliably?please don’t say gitlab

grep -rli search_this some-repo # (or use rg if you prefer)

Re: GitHub introduces sub-issues, issue types and advanced search

#84

Post by Sytten »

alexpovel wrote: post #81
hamandcheese wrote: post #48

A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.

Agree! For fun, I had put together a GitHub bot for this purpose a while ago. It indexes all existing issues in a repo, creates embeddings and stores them in a vector DB. When a new issue is created, the bot comments with the 3 most similar, existing issues, from vector similarity. In theory, that empowers users to close their own issues without maintainer intervention, provided an existing & solved issue covers thei…

We made a similar thing too for our community discord where you can add an Emoji on a message and it will look for similar issues with a simple RAG. That saves us so much time when a user asks if a feature is planned or not. We also ask them to go upvote the issue or create one in the response.

Not open source right now but if people are interested I could clean up the code.

Re: GitHub introduces sub-issues, issue types and advanced search

#85

Post by Sytten »

hamandcheese wrote: post #48

A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.

Ideally there should even be an API for it so we can use it in other systems like slack/discord bots when people suggest improvements.

Re: GitHub introduces sub-issues, issue types and advanced search

#86

Post by smarx007 »

alexpovel wrote: post #81
hamandcheese wrote: post #48

A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.

Agree! For fun, I had put together a GitHub bot for this purpose a while ago. It indexes all existing issues in a repo, creates embeddings and stores them in a vector DB. When a new issue is created, the bot comments with the 3 most similar, existing issues, from vector similarity. In theory, that empowers users to close their own issues without maintainer intervention, provided an existing & solved issue covers thei…

Microsoft seems to use a similar bot themselves, not sure how it is called or whether it is OSS: https://github.com/microsoft/winget-cli/issues/4765#issuecom...

Re: GitHub introduces sub-issues, issue types and advanced search

#87

Post by smarx007 »

StableAlkyne wrote: post #10
Calzifer wrote: post #9

Great, a few more decades and it might become a usable bugtracker. What's next on the list? Maybe priority/severity or status/resolution? I helped on a quite large open source project for some time and loved working with Bugzilla. The announced switch to Github for that project was one reason I lost interest. I even prefer to work with a well administrated(!) Jira over Github issues.

> Maybe priority/severity or status/resolution? That's already possible with the tag system. At least, that's the most common use I see for repos that decide to use tags. How do you envision this differing?

Sorting by priority?

Re: GitHub introduces sub-issues, issue types and advanced search

#89

Post by rbetts »

Calzifer wrote: post #9

Great, a few more decades and it might become a usable bugtracker. What's next on the list? Maybe priority/severity or status/resolution? I helped on a quite large open source project for some time and loved working with Bugzilla. The announced switch to Github for that project was one reason I lost interest. I even prefer to work with a well administrated(!) Jira over Github issues.

Using Github issues as a manager of multiple teams using multiple repos in GitHub has so many gaps, I often wonder if I'm just doing it wrong. The multi-repo issues feature a few years back was a huge step forward but also is very incomplete, still. Multi-repo labels and milestones, for example, are an obvious missing feature.
Post reply on HN