From the course: Visual Studio: Source Control with Git and GitHub

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Understand when to clone a repository

Understand when to clone a repository - Visual Studio Tutorial

From the course: Visual Studio: Source Control with Git and GitHub

Start my 1-month free trial

Understand when to clone a repository

- [Instructor] GitHub is a public site that was created to foster open collaboration between people. When you host your repository in GitHub, it could be seen and accessed by millions of programmers and other people. The visibility and project permissions are set with the repository scope. When you host a repository on GitHub, you set the scope to private or public. A private repository is one that is not openly shared with the GitHub community. Its visibility is limited to the owner of the repo and any invited collaborators. In other words, if you don't have an invite, you won't know that the repository exists and you can't find it on the site. The other consideration is who can work with the repository, make commits, add branches, and contribute to the project? In private repos, these permissions are available for the owner and invited collaborators. It's a different story when the repository is public. Now anyone can…

Contents