1

using the following search query...

https://github.com/search?q=repo%3AOpeningDesign%2FOpeningDesign+GET&p=1&ref=searchbar&type=Code&l=

..on this public repo: https://github.com/OpeningDesign/OpeningDesign

nothing shows up.

Am i missing something?

Ryan Schultz
  • 307
  • 4
  • 17
  • Just tried it with your example and a couple of others - and it doesn't work. Looks like code search with repo: and other options doesn't work at the moment. I suggest you report this to GitHub support folks. – Ivan Zuzak Jan 06 '13 at 10:38

1 Answers1

2

Update January 24th, 2013: source "A Whole New Code Search"

The same query repo:OpeningDesign/OpeningDesign GET now returns result!

The search index must have been updated when then new search engine has been deployed (elasticsearch.org)

Original answer (January 6th, 2013)

Considering that:

it seems to be an indexation issue.

After their recent fileservers issues, this could be a side-effect.
As Iven points out, GitHub support should be able to clarify this.

The support did clarify (07 January 2013):

We have stopped adding newly pushed code into our codesearch index.

The volume of code has outgrown our current search index, and we are working on moving to a more scalable search architecture.
I'm sorry for the annoyance.
We do not have an estimate for when this new search index will be up and running, but when it is ready a blog post will be published (GitHub blog)

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • zonks... looks major. Thanks @VonC – Ryan Schultz Jan 06 '13 at 18:29
  • Update from github: *"Hello Ryan, We have stopped adding newly pushed code into our codesearch index. The volume of code has outgrown our current search index, and we are working on moving to a more scalable search architecture. I'm sorry for the annoyance. We do not have an estimate for when this new search index will be up and running, but when it is ready a blog post will be published (https://github.com/blog)."* – Ryan Schultz Jan 08 '13 at 02:07
  • @RyanSchultz Thank you for the feedback. I have included it in the answer for more visibility. – VonC Jan 08 '13 at 06:27