And soon it will require an Outlook or Live account, no doubt.

It always has for me. I was forced to use my gh logged in browser when I wanted that feature.

AIUI previously it required people to be logged in when doing global- or (multi-repo) organisation-scoped searches but would also sometimes show "0" or "?" in results for single repo-scoped searches via "/"--until the "Code" section was clicked.

But with all the A/B testing on sites these days it's entirely possible for two people to have very different site interactions, so... shrug

Or just use grep.app

One month later and GitHub still hasn’t addressed the issue of inability to sort searches by new. This is despite their announcement having hundreds of downvotes and equally as many comments saying the new search is terrible.

Pathetic.

Depending on ones needs for search, a shout-out to Sourcegraph (https://sourcegraph.com/search) which in addition to offering anonymous search also supports regex searches and -- perhaps most relevant -- "go to symbol" for a huge number of cases. That alone can often save a "search" because it understands the relationships in the text

It's painless to use them because they have mapped the routes on sourcegraph.com to the github repo, so things like https://sourcegraph.com/github.com/kubernetes/kubernetes just magically work

I love them so much

We love you too

Hit this today weeding out npm dependency search results for a particular module.

Made yet another throwaway account to do the searches.

I can't see how making my research harder helped anyone.

no worries. check out https://github1s.com, just s/github/github1s/ on any URL and you will get a read-only VSCode viewer of the repo source code. It also comes with partial support to jump between symbols.

As no justification was given for the change, I'm led to assume that it's because telemetry data gathered via logged in people is more valuable...

(...and that there is insufficient competition in the market to prevent the change.)

Guess it's time to learn how to use git's local search tools properly...

(Or, more realistically, use a site- & url-scoped search on DuckDuckGo...)