Why do the results for an exact string search include mostly items that do not contain the exact string ?

[Josverl]

Topic

Search Syntax for exact matches containing forward slashes

Details

I tried to find discussions that contained the ID of a docker container using the exact string micropython/unix.

In order to be truthful when I tick the box in the right bottom : [ ] I have done a search for similar discussions*

For that I entered in double-quotes : "micropython/unix" , with the resulting URL : https://github.com/orgs/micropython/discussions?discussions_q=is%3Aopen+%22micropython%2Funix%22 .

The result set has many/mostly items that include EITHER micropython OR 'unix' , rather than the full string as specified.
attempts at escaping the / by `/' or '//' did not improve matters

Similar results if I try to do an advanced query

What is a working search syntax for such a query ?
bonus point if that works anywhere in GH

[SmileEngineer]

Hi,

To enhance the effectiveness of your exact string searches on GitHub, consider the following professional recommendations:

1. Utilize Double Quotes: Enclose your search term in double quotes, such as "micropython/unix", to specify that you are seeking that exact phrase.

2. Escape Special Characters: If your search term includes special characters like slashes, ensure to escape them, for example, \"micropython\/unix\".

3. Leverage Advanced Search Features: Explore GitHub's advanced search capabilities to filter results by repositories, issues, or discussions, thereby refining your search outcomes.

4. Review Search Settings: Verify that the appropriate search filters are activated to align with your query.

5. Provide Feedback: If you consistently encounter irrelevant results, consider submitting feedback to GitHub to assist in improving their search functionality.

6. Experiment with Variations: Adjust your search terms slightly to explore related discussions or issues that may not match exactly but are still pertinent.

Implementing these strategies should significantly improve the relevance of your search results on GitHub.

Hope Help, ^_^

[SmileEngineer]

Yes, I use ChatGPT, but I am not totally relying on it. I think you can confirm in my other posts.
As you know, now AI era, we use AI tool. It's not bad opinion.

[SmileEngineer]

One more thing, I think GitHub's search algorithm not only searches the subject but also the content.

I asked and was trying to solve problem with my total concern. I don't know why think narrowly.

[SmileEngineer]

We are in here to solve problems, This is not to slander or defame anyone.

[LiteBrite82]

@Josverl, Thank you for giving honest and direct feedback to community members; It helps us all grow together.
@BrotherRabbit91, Thank you for all of your contributions to our community; Your willingness to engage and provide help where you can is inspiring.

PS. I'm still looking for answers to your question

[aspark21]

actually, 2 was a very useful suggestion. Thanks

[LiteBrite82]

@Josverl
I checked with some folks on the dev team; it looks like your search parameters are correct. The problem is with the limitations of the search function in Discussions.
Ill tag this as a product enhancement (Its not quite a bug from a technical standpoint, but close)

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[markseuffert]

@Josverl, I do run into the same problem from time to time. As far I know the search function has two unusual behaviours. You can't search for an exact string wrapped in quotes, as you mentioned. You also can't search for incomplete words or the beginning of words, for example leader won't find leaderboard, as previously reported in #74744.

[Josverl]

Thanks for chiming in, feedback is fuel for innovation

[Josverl]

Dear James,
Please read the above and learn why, unfortunately, this is not true in this case.

Read, Reflect, Respond.

[RidmaShehan]

Why do the results for an exact string search include mostly items that do not contain the exact string?

GitHub search does not work as a strict exact-match search, even when you wrap your query in quotes.

Why this happens

1. Token-based search (not literal string matching)

GitHub breaks text into tokens (words) and matches them based on relevance, not by matching the full string character-by-character.

2. Quotes affect ranking, not filtering

Using quotes ("exact string") tells GitHub to prioritize results containing that phrase, but it does not guarantee that every result will include the exact string.

3. Stemming and normalization

GitHub may match:

• Different casing
• Singular vs plural
• Word variations
• Related terms

4. Relevance-based ranking

Search results are ordered by what GitHub considers most relevant, not by strict correctness. Partial matches or nearby terms can rank higher.

5. Multiple fields are searched

Matches may come from:

• Titles
• Descriptions
• Comments
• File paths
• Metadata

Even if the string is not visible in the main content, it may exist elsewhere.

6. Indexing and performance trade-offs

GitHub’s search is optimized for speed and scale, not perfect precision. Enforcing true exact-string matching everywhere would be expensive and slow.

How to get closer to exact matches

Use advanced search qualifiers:

"exact string" in:file
"exact string" in:title
"exact string" repo:owner/repo

[Josverl]

The issue was already acknowledged in https://github.com/orgs/community/discussions/131132#discussioncomment-10341867
please read the original problem statement, to avoid adding just grey noise.