263
GitHub: Can no longer search code without being logged in (github.com)
submitted 2 years ago* (last edited 2 years ago) by to c/programming@programming.dev
59 comments fedilink hide all child comments
 

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/

you are viewing a single comment's thread
view the rest of the comments
[–] 37 points 2 years ago (5 children)

lol? That must have been a half ass attempt on your part because GitHub search is fantastic.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 11 points 2 years ago (2 children)

    must have been a half ass attempt

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 6 points 2 years ago (1 child)

    Can you elaborate on what happened when you tried to search? I’ve never had trouble.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 2 years ago*

    Do you expect something as basic as a search to put up a fight?

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 6 points 2 years ago (2 children)

    Agreed their search is legendary

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago

    This is news to me. I've been cloning and searching for years because web search was useless. And by useless I mean - I know the word I'm looking for appears in exactly four places, formatted and capitalized exactly this way - and GitHub web search still doesn't find it.

    It wouldn't surprise me if it's gotten massively better - but only in the way that choosing to ride a bicycle to work is a massive improvement over sitting on a random rock.

  • permalink
  • fedilink
  • source
  • parent
  • [+] 2 points 2 years ago (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 2 years ago* (1 child)

    Just use the search bar... the only one they have that is on every page at the top right. That takes you to the results which defaults to code, but you can change it on the side to show repos, issues, prs, etc. You can even limit it to single repos or whole organisations.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] 1 point 2 years ago (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago* (last edited 2 years ago) (2 children)

    You used the wrong search bar, you just used the one for the file list.
    There is a search icon on the top right.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    You used the wrong search bar, you just used the one for the file list.

    The fact that one of the excuses for GitHub search results being subpar is that there is a right and a wrong search bar is already telling.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago

    The fact you call it "search results being subpar" tell me you never used the big top search bar labeled "Type / to search".
    You can't make an interface that everyone will understand, there will always be a percentage of user who will be lost.

  • permalink
  • fedilink
  • source
  • parent
  • [+] 0 points 2 years ago (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 2 years ago (1 child)

    I mean what view do you even get in this case ?
    The code tab, shows... code ?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago

    I don't find the search too bad but what does make it difficult is digging through a million forks of a library. Sometimes I want to find how other people used an obscure library method and I end up having to wade through endless forks with the same repeated bit of code.

    This is more a complaint of people using forking as a like button but I do wish there was an option to exclude them from search.

  • permalink
  • fedilink
  • source
  • parent