Skip to content

Latest commit

 

History

History
39 lines (30 loc) · 2.58 KB

searching-in-forks.md

File metadata and controls

39 lines (30 loc) · 2.58 KB
title intro redirect_from versions topics
Searching in forks
By default, forks are not shown in search results. You can choose to include them in repository searches, and in code searches if they meet certain criteria.
/articles/searching-in-forks
/github/searching-for-information-on-github/searching-in-forks
/github/searching-for-information-on-github/searching-on-github/searching-in-forks
fpt ghes ghec
*
*
*
GitHub search

To show forks in repository search results, add fork:true or fork:only to your query. For more information, see "AUTOTITLE."

{% ifversion ghes %}Forks are only indexed for code search when they have more stars than the parent repository. You will not be able to search the code in a fork that has fewer stars than its parent. To show forks with more stars than the parent repository in code search results, add fork:true or fork:only to your query. For more information, see "AUTOTITLE."{% endif %}

{% note %}

Note: Forks can only be included in repository and code searches.

{% endnote %}

The fork:true qualifier finds all results that match your search query, including forks. The fork:only qualifier finds only forks that match your search query.

Qualifier Example
fork:true github fork:true matches all repositories containing the word "github," including forks.
language:LANGUAGE fork:true android language:java fork:true matches code with the word "android" that's written in Java, in both forks and regular repositories.
fork:only github fork:only matches all fork repositories containing the word "github."
forks:>n fork:only forks:>500 fork:only matches repositories with more than 500 forks, and only returns those that are forks.

Further reading