Improved search for GitHub Issues in public preview �� #185760
Replies: 47 comments 44 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.
-
|
Nice |
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.
-
|
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.
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.
-
|
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.
-
|
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.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Release |
Beta Was this translation helpful? Give feedback.
-
|
Pueden hacer que los cheats por ejemplo de PSP funcionen permanentemente es decir que se estén sobreescribiendo cada segundo ya que después de una cinemática de un juego se desactivan y hay que volverlos a poner manualmente |
Beta Was this translation helpful? Give feedback.
-
Why do I need to put " " to find the text littearlly in the title .... |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Is this available in the CLI by chance or just in the web UI? |
Beta Was this translation helpful? Give feedback.
-
|
I want to be able to set the number of items per page to something higher than what's there. |
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.
-
|
Well I guess y'all are helping him hack my account . |
Beta Was this translation helpful? Give feedback.
-
|
Thanks oll
শনি, ২৮ ফেব, ২০২৬ ৪:৩৭ PM তারিখে Andrés ***@***.***> লিখেছেন:
… https://www.govinfo.gov/app/details/CFR-2025-title2-vol1
—
Reply to this email directly, view it on GitHub
<#185760 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B5S7WTHZ3KVRAZALH73UUTL4OFVWBAVCNFSM6AAAAACTB4G3LCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJVGQZDOOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Please stop trying to guess what I mean in my searches. I know what I mean. I'll type what I mean. Google does this and it's extraordinarily frustrating. Don't be like Google. |
Beta Was this translation helpful? Give feedback.
-
What kind of a metric is that anyway? (A successful search result is a diffuse concept, I would say, there can be multiple matching results or related topics/partial matches; also, success can mean to no find a result for the given query (and this is where some sort of reliability is key that natural language seemingly search cannot offer). It's not always "the issue you need".) If the average position of the successful result already was 4 with the standard search, that's extremely good. And if you over-optimize this to a value around 3 by sacrificing reliability, how does this affect the time to reach the successful result or the number of attempts (submitting the search)? Also, over what kind of searches are you averaging to judge performance? A frequent usecase (for me this could be well >25% of my github usage) is to search for (parts of) an error message to see related issues. Typing quotes each time instead of just Cmd+V and Enter is inconvenient. But probably necessary in the current state. We are in programming. Exact matches matter (more or less, modulo case sensitivity etc.). If I go to https://github.com/flutter-webrtc/flutter-webrtc and search for webrtc-sdk (the name of a dependency of that package), I am looking for issues containing the name of that dependency, and natural language search results are useless. P.S.: What is displayed in the abscissa in the graph in the first post? :D P.P.S.: What I mean by "reliability" of the search, I'm not 100% certain myself, but part of it is that I can somehow understand the search result or the relation between the query and the list of results that are shown. For the natural language search this is an unclear thing to me. P.P.P.S.: Thinking about pasting search terms, where you do not want to type extra quotes, and comparing to natural language search where, I assume, you would be typing in the query anyway, would it be sensible to swap things around, i.e. have the "normal" search on by default and activate the natural language search through some extra characters (quotes, or "nat:query" etc. etc.)? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.

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