- cross-posted to:
- tech@kbin.social
- technology@lemmy.ml
- cross-posted to:
- tech@kbin.social
- technology@lemmy.ml
Edit:
Since theres been some confusion with dates
In 2016 github made site side searching login only and hid the search bar if you werent logged in. This didnt include searching within a repository so that could still be done, just not all repositories
This year was the change being referred to in this link which made repository level searching require logging in
Blog post: https://github.blog/changelog/2023-06-07-code-search-now-requires-login/
How hard do you need to try to use a feature for it to be considered decent? Do you expect something as basic as a search to put up a fight?
Can you elaborate on what happened when you tried to search? I’ve never had trouble.
GitHub search simply won’t find search terms that I know are there (because I can grep them in my local repo). It also fails to search all branches. There’s also insufficient filtering for filetypes or paths.
Maybe I’m just spoiled from having used OpenGrok, as well as knowing how to use basic tools like find and grep, all of which I find substantially more useful.
Increasingly, you should be. Search algorithms from Amazon to Google are getting deliberately enshittified in order to force you to see what they want you to see instead of finding what you were actually looking for. For example, things like quotation marks and the minus operator no longer work. I would be supremely unsurprised to learn of Microsoft following suit.