Creating a repository on GitHub
After you create your repository on GitHub Enterprise, you can customize its settings and content.
A repository is like a folder for your project. Your project's repository contains all of your project's files and stores each file's revision history. You can also discuss and manage your project's work within the repository.
About repository visibility→
You can restrict who has access to a repository by choosing a repository's visibility: public or private.
Creating a new repository→
You can create a new repository on your personal account or any organization where you have sufficient permissions.
You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.
About code owners→
You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.
About repository languages→
The files and directories within a repository determine the languages that make up the repository. You can view a repository's languages to get a quick overview of the repository.
Licensing a repository→
Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.
Creating an issues-only repository→
GitHub Enterprise does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.
Limits for viewing content and diffs in a repository→
Certain types of resources can be quite large, requiring excessive processing on GitHub Enterprise. Because of this, limits are set to ensure requests complete in a reasonable amount of time.
Duplicating a repository→
To duplicate a repository without forking it, you can run a special clone command, then mirror-push to the new repository.