A repository contains all of your code, your files, and each file's revision history. You can discuss and manage your work within the repository.
About repositoriesA repository is the most basic element of GitHub. It's a place where you can store your code, your files, and each file's revision history. Repositories can have multiple collaborators and can be either public or private.
To create a new repository, go to https://github.com/new. For instructions, see Quickstart for repositories.
Repository terminologyBefore getting started with repositories, learn these important terms.
About repository ownershipYou can own repositories individually, or you can share ownership of repositories with other people in an organization.
In either case, access to repositories is managed by permissions. For more information, see Permission levels for a personal account repository and Repository roles for an organization.
About collaborationYou can use repositories to manage your work and collaborate with others.
With GitHub Free for personal 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. For more information, see GitHub’s plans.
About repository visibilityYou can restrict who has access to a repository by choosing a repository's visibility: public or private.
When you create a repository, you can choose to make the repository public or private. Repositories in organizations that use GitHub Enterprise Cloud and are owned by an enterprise account can also be created with internal visibility. For more information, see the GitHub Enterprise Cloud documentation.
Public repositories expose your codebase to everyone, increasing the risk that attackers might exploit vulnerabilities or access sensitive information. You can mitigate these risks by enabling GitHub security features such as Dependabot, secret scanning, push protection, and code scanning for the repository. Additionally, you should add a security policy (a SECURITY.md
file) to your repository, that outlines how vulnerabilities should be reported, to ensure that potential threats are addressed efficiently.
Although private repositories restrict access to authorized users, it's still essential to implement strong access controls, multi-factor authentication, and regular audits to mitigate risks.
For more information, see Quickstart for securing your repository.
Organization owners always have access to every repository created in an organization. For more information, see Repository roles for an organization.
People with admin permissions for a repository can change an existing repository's visibility. For more information, see Setting repository visibility.
Next stepsHere are some helpful resources for taking your next steps with repositories.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4