GitHub Community
Improved search for GitHub Issues in public preview 🔍 #185760
Replies: 32 comments 25 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Nice |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
This is my working.and... |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Should the old search syntax still work? I used to search PRs with this search syntax: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @rap1ds quick update, while not related to the release of semantic search, one of our engineers was able to replicate the issue and is investigating it. Thanks for raising it! |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
The semantic search feature is interesting, and I could see it being useful. However, currently the decision to change the default sort order of search results away from newest to the nebulous "best match" is a significant usability hindrance. I found the search results not being ordered by newest as quite surprising, and notably less useful. In almost all cases an issue created a week ago is going to be more relevant than one created a year ago, even if the search term matches less exactly. Even when using quoting to avoid semantic search, it still uses the best match search order. While you can change the sort order after performing the search, there is no way I've found to persist this setting. In addition to likely being more useful, sorting by newest is much more predictable, which improves usability by ensuring the user feels in control. In a repository that the searcher is familar with, they will often be able to use the creation order of a PR to know if they need to look at newer or older issues, based on context outside of the query, such as when they remember an issue being discussed. Furthermore, if there are so many search results that the desired result is not visible on the first page, the query likely needs refinement, rather than sorting in a different order. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @jfrost-mo and thanks for your feedback! As the PM on this, I wanted to take the time to respond, and also to explain our internal reasoning for this change. It seems that the usefulness of one sort vs another is use-case dependent - our metrics show that, overall, 'best match' returns consistently more relevant results to users. This is because a lot of issues searching takes place when users are looking to find further information or troubleshoot. In those kinds of cases, they are often agnostic to when the issue was created. With that being said, I hear that, in your work, you are more interested in accessing newer issues first as you cross-reference with relevant PRs. That makes perfect sense to me, and I understand that having to change the sort every time feels like extra friction that has been introduced to your workflow - especially without the ability to persist your sort preference. I'd like to collect some more data around this problem and think through solutions. And thanks again for taking the time to outline your perspective! |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps it depends on familiarity on the codebase. Within my own codebase I approximately know what issues there are, so its useful for them to be presented consistently and predictably. However on an unfamiliar codebase you would not have the experience to compare to, so it may be less of an issue. As a counter point, the experience that got me to send this feedback was on an unfamiliar repository. I was reporting an issue in dependabot that was related to a recent feature removal, and wanted to check it had not yet been reported. Therefore after putting in my search query I was only interested in issues reported since around when that feature was removed, and not older issues about changes or problems with the feature. The best match made discovering the issues difficult, and I could not be confident that I had covered the range where the issue could have been raised, necessitating looking through multiple pages of output. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
It would be so helpful to have this functionality in GitHub Projects—at least boolean operators. 🙏🏻 🙂 |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Hi - would be really nice if one could select issues and apply actions as in milestones view (ex. https://github.com/wrye-bash/wrye-bash/milestone/19) in the search view (ex. https://github.com/wrye-bash/wrye-bash/issues?q=%20label%3AA-scripts) |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Just wanted to chime in and say that it's been working quite well for me. Finds a bunch of issues about the same problem, even if they don't include the words from the search query. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
This seems to mess up the old syntax when I try to use |
Beta Was this translation helpful? Give feedback.
-
|
@seankhliao thanks for bringing this up, I added it to our board 🙏🏼 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks
null
2:25 AM এ শুক্র, 6 ফেব, 8 Reiwa এ Ab Salam Munsi ***@***.***>
লিখেছেন:
… thank you
—
Reply to this email directly, view it on GitHub
<#185760 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B5S7WTGMQ34S4COGOFHQSIL4KORMJAVCNFSM6AAAAACTB4G3LCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZRGEZDGMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Добрый день уважаемые. У меня в HA не заработал Neptun Smart + tuya. Всё встало, но подключение Neptuna происходит по циклу примерно 10 сек. Включается и потом выключается и так циклично. |
Beta Was this translation helpful? Give feedback.
-
|
Лог вставился. |
Beta Was this translation helpful? Give feedback.
-
|
Does this currently apply to the graphql api search endpoint? query Search() {
search(query: org:my-org is:issue state:open sort:relevance-desc sweet search, type: ISSUE, first: 100) {
nodes {
... on Issue {
number
title
bodyText
url
}
}
}
} |
Beta Was this translation helpful? Give feedback.
-
|
El lun., 9 de febrero de 2026 14:19, Jake Tigchelaar <
***@***.***> escribió:
… Does this currently apply to the graphql api search endpoint?
If not currently, will it when this is offically released?
query Search($query: String!, $type: SearchType!) {
search(query: org:my-org is:issue state:open sort:relevance-desc sweet search, type: ISSUE, first: 100) {
nodes {
... on Issue {
number
title
bodyText
url
}
}
}
}
—
Reply to this email directly, view it on GitHub
<#185760 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B5SWY2UMTOWNBIADIYF3HD34LDTWPAVCNFSM6AAAAACTB4G3LCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZUHAZDGOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
El lun., 9 de febrero de 2026 17:53, Victor Hugo Ortiz Leon <
***@***.***> escribió:
…
El lun., 9 de febrero de 2026 14:19, Jake Tigchelaar <
***@***.***> escribió:
> Does this currently apply to the graphql api search endpoint?
> If not currently, will it when this is offically released?
>
> query Search($query: String!, $type: SearchType!) {
> search(query: org:my-org is:issue state:open sort:relevance-desc sweet search, type: ISSUE, first: 100) {
> nodes {
> ... on Issue {
> number
> title
> bodyText
> url
> }
> }
> }
> }
>
> —
> Reply to this email directly, view it on GitHub
> <#185760 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/B5SWY2UMTOWNBIADIYF3HD34LDTWPAVCNFSM6AAAAACTB4G3LCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZUHAZDGOI>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***
> .com>
>
|
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
why is there no option to turn it off? |
Beta Was this translation helpful? Give feedback.
-
|
There is. You can turn it off from the feature preview dialog. |
Beta Was this translation helpful? Give feedback.
-
|
does that mean i won't be able to disable it once the feature is fully released and no longer in preview? most of the time i don't want results that don't contain the exact words i searched for. sometimes it's useful, but it should be a toggle that can be easily switched on and off for each search |
Beta Was this translation helpful? Give feedback.
-
|
You can just put quotes for exact match
|
Beta Was this translation helpful? Give feedback.
-
|
Does this work in Github Projects? |
Beta Was this translation helpful? Give feedback.
-
|
Nice |
Beta Was this translation helpful? Give feedback.
-
|
yap
…On Fri, Feb 13, 2026 at 11:51 AM md masud rana ***@***.***> wrote:
Nice
—
Reply to this email directly, view it on GitHub
<#185760 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B6DMA7BG24XDGE3F4HUV5SL4LWGCHAVCNFSM6AAAAACTB4G3LCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZZGMZDCOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
query Search() { |
Beta Was this translation helpful? Give feedback.
-
|
Thanks
…On Mon, Feb 16, 2026, 7:25 AM ANDRES ***@***.***> wrote:
query Search() {
search(query: org:my-org is:issue state:open sort:relevance-desc sweet
search, type: ISSUE, first: 100) {
nodes {
... on Issue {
number
title
bodyText
url
}
}
}
}
—
Reply to this email directly, view it on GitHub
<#185760 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B5S7WTAS2AKENJL3B4XSVVD4MEMCBAVCNFSM6AAAAACTB4G3LCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOBRG4YDCNY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It's now easier than ever to find exactly the issue you're looking for with our improved search for GitHub Issues. Built on our new semantic index, you can now find results based on the meaning of your query not just the keywords you use.
What's new
Search for issues using natural language like "authentication failing on mobile" or "funny timeline behavior", and GitHub returns conceptually similar results, even if the issue titles or descriptions use completely different wording. The more descriptive your query, the better your results.
Our prerelease testing has found that this produces significantly better results for users. Overall, users of our semantic search find the issue they need 25% higher up the list than traditional search.
How it works
Semantic search activates when you describe what you're looking for in natural language. To make best use of this, results are now automatically ordered by "Best match" to surface the most relevant issues first.
For searches that need exact matching (e.g. queries with quotation marks) GitHub uses the traditional, lexical search engine to give you the precision you need.
During public preview, you can opt out using the feature preview dialog.
How to try it
Head to any repository's Issues tab and search using natural language.
🌟Leave a comment!
Join the discussion and leave feedback in the comments below!
Additional improvements to issues and projects
Beta Was this translation helpful? Give feedback.
All reactions