このバージョンの GitHub Enterprise はこの日付をもって終了となります: 2022-02-16. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、最新バージョンのGitHub Enterpriseにアップグレードしてください。 アップグレードに関する支援については、GitHub Enterprise supportに連絡してください。

Searching for repositories

You can search for repositories on GitHub Enterprise Server and narrow the results using these repository search qualifiers in any combination.

You can search for repositories globally across all of your GitHub Enterprise Server instance, or search for repositories within a particular organization. For more information, see "About searching on GitHub."

To include forks in the search results, you will need to add fork:true or fork:only to your query. For more information, see "Searching in forks."

ヒント:

  • この記事には、GitHub.com のウェブサイトでの検索例へのリンクが含まれていますが、同じ検索フィルターは GitHub Enterprise Server でも使えます。 リンクされている検索例で、github.comをyour GitHub Enterprise Server instanceのホスト名で置き換えてください。
  • 検索結果を改良する検索修飾子を追加できる検索構文のリストについては、「検索構文を理解する」を参照してください。
  • 複数単語の検索用語は引用符で囲みます。 たとえば "In progress" というラベルを持つ Issue を検索したい場合は、label:"in progress" とします。 検索では、大文字と小文字は区別されません。

Search by repository name, description, or contents of the README file

With the in qualifier you can restrict your search to the repository name, repository description, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name and description are searched.

QualifierExample
in:namejquery in:name matches repositories with "jquery" in the repository name.
in:descriptionjquery in:name,description matches repositories with "jquery" in the repository name or description.
in:readmejquery in:readme matches repositories mentioning "jquery" in the repository's README file.
repo:owner/namerepo:octocat/hello-world matches a specific repository name.

Search based on the contents of a repository

You can find a repository by searching for content in the repository's README file using the in:readme qualifier. For more information, see "About READMEs."

Besides using in:readme, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "Finding files on GitHub" and "Searching code."

QualifierExample
in:readmeoctocat in:readme matches repositories mentioning "octocat" in the repository's README file.

Search within a user's or organization's repositories

To search in all repositories owned by a certain user or organization, you can use the user or org qualifier.

QualifierExample
user:USERNAMEuser:defunkt forks:>100 matches repositories from @defunkt that have more than 100 forks.
org:ORGNAMEorg:github matches repositories from GitHub.

Search by repository size

The size qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "Understanding the search syntax."

QualifierExample
size:nsize:1000 matches repositories that are 1 MB exactly.
size:>=30000 matches repositories that are at least 30 MB.
size:<50 matches repositories that are smaller than 50 KB.
size:50..120 matches repositories that are between 50 KB and 120 KB.

Search by number of followers

You can filter repositories based on the number of users who follow the repositories, using the followers qualifier with greater than, less than, and range qualifiers. For more information, see "Understanding the search syntax."

QualifierExample
followers:nnode followers:>=10000 matches repositories with 10,000 or more followers mentioning the word "node".
styleguide linter followers:1..10 matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter."

Search by number of forks

The forks qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "Understanding the search syntax."

QualifierExample
forks:nforks:5 matches repositories with only five forks.
forks:>=205 matches repositories with at least 205 forks.
forks:<90 matches repositories with fewer than 90 forks.
forks:10..20 matches repositories with 10 to 20 forks.

Search by number of stars

You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "Saving repositories with stars" and "Understanding the search syntax."

QualifierExample
stars:nstars:500 matches repositories with exactly 500 stars.
stars:10..20 matches repositories 10 to 20 stars, that are smaller than 1000 KB.
stars:>=500 fork:true language:php matches repositories with the at least 500 stars, including forked ones, that are written in PHP.

Search by when a repository was created or last updated

You can filter repositories based on time of creation or time of last update. For repository creation, you can use the created qualifier; to find out when a repository was last updated, you'll want to use the pushed qualifier. The pushed qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository.

Both take a date as a parameter. 日付の形式は ISO8601標準に従い、YYYY-MM-DD(年-月-日) とする必要があります。 オプションの時間情報のTHH:MM:SS+00:00を日付の後に付けて、時、分、秒で検索できるようにすることもできます。 これはTの後にHH:MM:SS(時-分-秒)、そしてUTCオフセット(+00:00)を続けたものです。

日付に対して検索を行う場合、結果をさらにフィルタリングするためにより大きい、より小さい、範囲の修飾子を利用できます。 詳しい情報については、「検索構文を理解する」を参照してください。

QualifierExample
created:YYYY-MM-DDwebos created:<2011-01-01 matches repositories with the word "webos" that were created before 2011.
pushed:YYYY-MM-DDcss pushed:>2013-02-01 matches repositories with the word "css" that were pushed to after January 2013.
case pushed:>=2013-03-06 fork:only matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks.

Search by language

You can search repositories based on the language of the code in the repositories.

QualifierExample
language:LANGUAGErails language:javascript matches repositories with the word "rails" that are written in JavaScript.

Search by topic

You can find all of the repositories that are classified with a particular topic. For more information, see "Classifying your repository with topics."

QualifierExample
topic:TOPICtopic:jekyll matches repositories that have been classified with the topic "jekyll."

Search by number of topics

You can search repositories by the number of topics that have been applied to the repositories, using the topics qualifier along with greater than, less than, and range qualifiers. For more information, see "Classifying your repository with topics" and "Understanding the search syntax."

QualifierExample
topics:ntopics:5 matches repositories that have five topics.
topics:>3 matches repositories that have more than three topics.

Search by license

You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "Licensing a repository."

QualifierExample
license:LICENSE_KEYWORDlicense:apache-2.0 matches repositories that are licensed under Apache License 2.0.

Search by repository visibility

You can filter your search based on the visibility of the repositories. For more information, see "About repositories."

QualifierExample
is:publicis:public org:github matches public repositories owned by GitHub.
is:internalis:internal test matches internal repositories that you can access and contain the word "test".
is:privateis:private pages matches private repositories that you can access and contain the word "pages."

Search based on whether a repository is archived

You can search repositories based on whether or not the repositories are archived. For more information, see "Archiving repositories."

QualifierExample
archived:truearchived:true GNOME matches repositories that are archived and contain the word "GNOME."
archived:falsearchived:false GNOME matches repositories that are not archived and contain the word "GNOME."

Further reading

このドキュメントは役立ちましたか?

プライバシーポリシー

これらのドキュメントを素晴らしいものにするのを手伝ってください!

GitHubのすべてのドキュメントはオープンソースです。間違っていたり、はっきりしないところがありましたか?Pull Requestをお送りください。

コントリビューションを行う

OR, コントリビューションの方法を学んでください。

問題がまだ解決していませんか?