Downloading files from GitHub

Introduction

There are different ways to get a copy of a repository's files on GitHub Enterprise Server. You can:

Download a snapshot of a repository's files as a zip file to your own (local) computer.
Clone a repository to your local computer using Git.
Fork a repository to create a new repository on GitHub.

Each of these methods has its own use case, which we'll explain in the next section.

This tutorial focuses on downloading a repository's files to your local computer. For example, if you've found some interesting content in a repository on GitHub Enterprise Server, downloading is a simple way to get a copy of the content, without using Git or applying version control.

Understanding the differences between downloading, cloning, and forking

Term	Definition	Use case
Download	To save a snapshot of a repository's files to your local computer.	You want to use or customize the content of the files, but you're not interested in applying version control.
Clone	To make a full copy of a repository's data, including all versions of every file and folder.	You want to work on a full copy of the repository on your local computer, using Git to track and manage your changes. You likely intend to sync these locally-made changes with the GitHub Enterprise Server-hosted repository. For more information, see "Cloning a repository."
Fork	To create a new repository on GitHub Enterprise Server, linked to your personal account, that shares code and visibility settings with the original ("upstream") repository.	You want to use the original repository's data as a basis for your own project on GitHub. Or, you want to use the fork to propose changes to the original ("upstream") repository. After forking the repository, you still might want to clone the repository, so that you can work on the changes on your local computer. For more information, see "Fork a repository."