Can't search repository for months. "Not indexed yet" "Try again later"

[LeoDavidson]

I'm unable to search my own small repository for strings in code.

The error message says the repository has not been indexed yet, and to try again later.

But I've been trying for months now, I think, and the indexing never happens.

At the moment, I have to download a zip of my repository in order to search it locally.

Full error message, which includes the repository name:

This repository's code has not been indexed yet. Try again later.
repo:LeoDavidson/discourse-directoryopus Directory

[jelmerk]

same

[mwa-corey]

I also have been experiencing this for months.
It appears it is only returning the message for certain search terms.

[diachun]

I am having the same issue. Any search inside my repos returns the message "This account's code is being indexed right now. Try again in a few minutes."
Is this feature actually in production for all accounts?

[ricosaurus]

Same. I looked for a solution, and supposedly, once an initial search was attempted, the indexing would begin (and one might assume, end). But that doesn't appear to be the case -- repositories that got the error message a month ago still do today. It would be more helpful to just be honest about it -- "Github isn't going to index your inconsequential project so quit trying to search it."

[AtomicRaven]

We pay for Github Enterprise - this is bullshit. Happens in half our projects.

[Markeli]

And how have you fixed it?

[thesunlover]

We pay for Github Enterprise - this is bullshit. Happens in half our projects.

Please let us know how you have fixed that?

[raisch]

Seriously considering saving my cash and going to a competitor that actually provides the service I pay for.

[AtomicRobotMan0101]

This is 100% bullshit.

The enshitification begins.

Who would care to wager there will soon be an option for "premium indexing"?

[devafortun]

hi, I suggest like this to solve that problem.

1. Confirm Repository Visibility
   Ensure that your repository is public. Private repositories may have limited search capabilities. You can check this by going to your repository settings:
   Navigate to Settings > General > Danger Zone.
   If it's private and you want it to be public, consider changing it (note that this will make your code visible to everyone).
2. Check for Recent Activity:
   GitHub typically indexes repositories based on activity. If your repository has been inactive for a long time, it might not be prioritized for indexing.
   Make a small change (like updating the README or adding a new file) and commit it. This can sometimes trigger re-indexing.
3. Add a README or Other Documentation:
   If your repository lacks a README file or other documentation, add one. GitHub may prioritize indexing repositories that have documentation, as it improves usability.
4. Use the Code Search Beta:
   GitHub has been rolling out new features for code search. If you haven't already, consider opting into the new code search experience:
   Go to your GitHub account settings and look for options related to "Beta features" or "Code Search."
   Enabling this feature may improve search functionality.
5. Wait for Indexing:
   After making changes or triggering actions that should prompt indexing, wait a bit (usually around 10-30 minutes) and try searching again.

If issue persists after trying above steps, I think it is a good idea to contact Github Support!
Best wishes

[thesunlover]

I'm currently using the Fine-grained personal access tokens (Preview) is that what you are referring to in point 4 (Use the Code Search Beta)?
Also, I am trying to do my search on a private personal test repo and it is not indexed, until I get access with a PAT to a private corporate repo. Is there a difference in the indexing priorities?

[harisdev-netizen]

hi, I suggest like this to solve that problem.

1. Confirm Repository Visibility
   Ensure that your repository is public. Private repositories may have limited search capabilities. You can check this by going to your repository settings:
   Navigate to Settings > General > Danger Zone.
   If it's private and you want it to be public, consider changing it (note that this will make your code visible to everyone).
2. Check for Recent Activity:
   GitHub typically indexes repositories based on activity. If your repository has been inactive for a long time, it might not be prioritized for indexing.
   Make a small change (like updating the README or adding a new file) and commit it. This can sometimes trigger re-indexing.
3. Add a README or Other Documentation:
   If your repository lacks a README file or other documentation, add one. GitHub may prioritize indexing repositories that have documentation, as it improves usability.
4. Use the Code Search Beta:
   GitHub has been rolling out new features for code search. If you haven't already, consider opting into the new code search experience:
   Go to your GitHub account settings and look for options related to "Beta features" or "Code Search."
   Enabling this feature may improve search functionality.
5. Wait for Indexing:
   After making changes or triggering actions that should prompt indexing, wait a bit (usually around 10-30 minutes) and try searching again.

If issue persists after trying above steps, I think it is a good idea to contact Github Support! Best wishes

My repository is currently active, and I am even working on it currently and still I am facing the following error:

This repository's code has not been indexed yet. Try again later.
repo:harisdev-netizen/runaway-theme language:SCSS

[devafortun]

Yes, there is.
Fine-grained PATs provide more specific permissions and control over repository access compared to the classic PATs, which is crucial for using features like Code Search effectively.
Regarding your search on a private personal test repository, it is important to note that indexing priorities can differ between private personal repositories and private corporate repositories. Typically, private repositories may not be indexed until specific access permissions are granted through a PAT.
In summary, if you want to ensure that your private personal test repository is indexed, you may need to check the permissions associated with your fine-grained PAT and confirm that it has been granted access to that specific repository.
If you allow me to use your Upwork account, I will give you extra income
or if you introduce me someone, I will appreciate with you

[acampove]

This is why I have two remotes, one in gitlab and the other in github. I have never had this problem in gitlab, there, this search just works.

[markus-zhang]

Doesn't work for me either. I guess I need to get another remote.

[LegalizeAdulthood]

I have also been experiencing this problem for months; the age of recent changes on the repository seems to have no bearing on whether or not the repository is searchable.