Article version: Enterprise Server 2.14

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-07-12. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Create a repo

To put your project up on your GitHub Enterprise Server instance, you'll need to create a repository for it to live in.

You can store a variety of projects in GitHub Enterprise repositories, including open source projects. With open source projects, you can share code to make better, more reliable software.

Note: You can create public repositories for an open source project. When creating your public repository, make sure to include a license file that determines how you want your project to be shared with others. For more information on open source, specifically how to create and grow an open source project, we've created Open Source Guides that will help you foster a healthy open source community by recommending best practices for creating and maintaining repositories for your open source project. You can also take a free GitHub Learning Lab course on maintaining open source communities.

  1. In the upper-right corner of any page, click , and then click New repository.

    Drop-down with option to create a new repository

  2. Type a short, memorable name for your repository. For example, "hello-world".

    Field for entering a repository name

  3. Optionally, add a description of your repository. For example, "My first repository on GitHub Enterprise."

    Field for entering a repository description

  4. Choose to make the repository either public or private. Public repositories are visible to the public, while private repositories are only accessible to you, and people you share them with. For more information, see "Setting repository visibility."

    Radio buttons to select private or public status

  5. Select Initialize this repository with a README.

    Checkbox to create a README when the repository is created

  6. Click Create repository.

Congratulations! You've successfully created your first repository, and initialized it with a README file.

Commit your first change

A commit is like a snapshot of all the files in your project at a particular point in time.

When you created your new repository, you initialized it with a README file. README files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your README file are automatically shown on the front page of your repository.

Let's commit a change to the README file.

  1. In your repository's list of files, click README.md.

    Readme file in file list

  2. Above the file's content, click .

  3. On the Edit file tab, type some information about yourself.

    New content in file

  4. Above the new content, click Preview changes.

    File preview button

  5. Review the changes you made to the file. You'll see the new content in green.

    File preview view

  6. At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see "Creating a commit with multiple co-authors."

    Commit message for your change

  7. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is master, you should choose to create a new branch for your commit and then create a pull request.

    Commit branch options

  8. Click Propose file change.

    Propose file change button

Celebrate

Congratulations! You have now created a repository, including a README file, and created your first commit on your GitHub Enterprise Server instance. What do you want to do next?

Ask a human

Can't find what you're looking for?

Contact us