filename: qualifier does not work anymore.

[Vyom-Yadav]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/search-github/searching-on-github/searching-code#search-by-filename

What changes are you suggesting?

Modify the file https://github.com/github/docs/blob/main/content/search-github/searching-on-github/searching-code.md#search-by-filename and other files which have this content.

filename: searching no longer works.

Link of example from docs: https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code

Output:

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[cmwilson21]

@Vyom-Yadav Thanks so much for opening an issue! I'll triage this for the team to take a look 👀

[roiros]

The example for searching by file-size doesn't work as well.
https://docs.github.com/en/search-github/searching-on-github/searching-code#search-by-file-size

The search example link
gets

Possible unrecognized qualifier, searching for this term literally
function size:>10000 language:python

[subatoi]

@Vyom-Yadav @roiros Please accept our apologies for the delay in getting back to you. I looked at the referenced issue and I think you may have already reached the correct conclusion, but just in case not:

The documentation you've linked to (everything under https://docs.github.com/en/search-github/searching-on-github/searching-code) is for a legacy implementation of code search. I think this may not have been the case when you first encountered this problem; the functionality you'd need is in any case described under https://docs.github.com/en/search-github/github-code-search/understanding-github-code-search-syntax#path-qualifier.

We'll see if we can do anything to improve the experience with the legacy documentation, but for now I'll close this issue. Please feel free to add another comment if there's anything outstanding you'd like to raise.

Thank you for your interest in helping to improve our docs! ✨