News for hackers. Stuff that matters.
Re:Changes to Code Search Indexing by OJFord on Thursday December 17, 2020 @02:44PM (#25459499)
Yep, but note it's requiring repo-level activity, not that it won't index a LoC that hasn't changed for a year.

So, 'anyone working on a larger codebase' has probably caused some activity on it within the last year.

I think it's fair enough, certainly if it were two or three years. Anyone who objects can have a GitHub Action amend an empty commit on an unused branch once a year anyway!

Re:Changes to Code Search Indexing by est31 on Thursday December 17, 2020 @04:23PM (#25460634)
Those are fair points. Larger projects often get split into multiple sub-projects, especially in git-age languages like ruby, js or Rust. The same rules apply there: often such projects get created by their original authors and then work for the most part, so don't see any changes for years. So the effects translate into multi-repo projects as well.

To give an example, in Rust the mime crate has over 14 million downloads, but the last git commit was in January 2020. So it will fall out of Github's search index soon, even though it's used by everyone who uses the reqwest crate, which is a lot of people.

In fact, likely some people will run cargo vendor and then upload the results to github often enough that it'll show up in search results, but instead of the canonical location you'll have to look at vendored repos... not really nice.