About repositories

A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository.

About repositories

You can own repositories individually, or you can share ownership of repositories with other people in an organization.

You can restrict who has access to a repository by choosing the repository's visibility. For more information, see "About repository visibility."

For user-owned repositories, you can give other people collaborator access so that they can collaborate on your project. If a repository is owned by an organization, you can give organization members access permissions to collaborate on your repository. For more information, see "Permission levels for a user account repository" and "Repository permission levels for an organization."

With GitHub Free for user accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. To get advanced tooling for private repositories, you can upgrade to GitHub Pro, GitHub Team, or GitHub Enterprise Cloud. 詳しい情報については「GitHubの製品」を参照してください。

You can use repositories to manage your work and collaborate with others.

  • You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "About issues."
  • ディスカッションでは、質問、質問への回答、情報の共有、発表、 プロジェクトについて会話を実施したり参加したりすることができます。 詳しい情報については「ディスカッションについて」を参照してください。
  • You can use pull requests to propose changes to a repository. For more information, see "About pull requests."
  • You can use project boards to organize and prioritize your issues and pull requests. For more information, see "About project boards."

リポジトリと個々のファイルには、サイズの制限があります。 詳しい情報については「ディスクの容量とは何か?」を参照してください。

About repository visibility

You can restrict who has access to a repository by choosing a repository's visibility: public, internal, or private.

When you create a repository, you can choose to make the repository public or private. If you're creating the repository in an organization that is owned by an enterprise account, you can also choose to make the repository internal.

Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to enterprise members. For more information, see "About internal repositories."

Organization owners always have access to every repository created in an organization. For more information, see "Repository permission levels for an organization."

People with admin permissions for a repository can change an existing repository's visibility. For more information, see "Setting repository visibility."

About internal repositories

Note: インターナルリポジトリはGitHub Enterprise Cloud、GitHub Enterprise Server 2.20+で利用できます。 詳しい情報については「GitHubの製品」を参照してください。

インターナルリポジトリを使って、Enterprise内で「インナーソース」を実践できます。 Enterpriseアカウントのメンバーは、プロプライエタリな情報をパブリックに共有することなく、オープンソースの方法論を用いてコラボレートできます。 For more information on innersource, see GitHub's whitepaper "An introduction to innersource."

All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people outside of the enterprise, including outside collaborators on organization repositories. For more information, see "Roles in an enterprise" and "Repository permission levels for an organization."

インターナルリポジトリは、Enterpriseアカウントが所有するOrganization内で作成されるすべての新規リポジトリのデフォルト設定です。

If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically.

Limits for viewing content and diffs in a repository

Certain types of resources can be quite large, requiring excessive processing on GitHub. Because of this, limits are set to ensure requests complete in a reasonable amount of time.

Most of the limits below affect both GitHub and the API.

Text limits

Text files over 512 KB are always displayed as plain text. Code is not syntax highlighted, and prose files are not converted to HTML (such as Markdown, AsciiDoc, etc.).

Text files over 5 MB are only available through their raw URLs, which are served through raw.githubusercontent.com; for example, https://raw.githubusercontent.com/octocat/Spoon-Knife/master/index.html. Click the Raw button to get the raw URL for a file.

Diff limits

Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views:

  • In a pull request, no total diff may exceed 20,000 lines that you can load or 1 MB of raw diff data.
  • No single file's diff may exceed 20,000 lines that you can load or 500 KB of raw diff data. Four hundred lines and 20 KB are automatically loaded for a single file.
  • The maximum number of files in a single diff is limited to 300.
  • The maximum number of renderable files (such as images, PDFs, and GeoJSON files) in a single diff is limited to 25.

Some portions of a limited diff may be displayed, but anything exceeding the limit is not shown.

Commit listings limits

The compare view and pull requests pages display a list of commits between the base and head revisions. These lists are limited to 250 commits. If they exceed that limit, a note indicates that additional commits are present (but they're not shown).

Further reading

このドキュメントは役立ちましたか?プライバシーポリシー

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

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

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

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

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

GitHubコミュニティで質問するサポートへの連絡