docs/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md

---
title: Adding an existing project to GitHub using the command line
intro: 'Putting your existing work on {{ site.data.variables.product.product_name }} can let you share and collaborate in lots of great ways.'
redirect_from:
  - /articles/add-an-existing-project-to-github/
  - /articles/adding-an-existing-project-to-github-using-the-command-line
versions:
  free-pro-team: '*'
  enterprise-server: '*'
---
{{ site.data.reusables.repositories.migrating-from-codeplex }}

{% tip %}

**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {{ site.data.variables.product.prodname_desktop }}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{{ site.data.variables.product.prodname_desktop }} Help*.

{% endtip %}

{{ site.data.reusables.repositories.sensitive-info-warning }}

{% mac %}

1. [Create a new repository](/articles/creating-a-new-repository) on {{ site.data.variables.product.product_location }}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {{ site.data.variables.product.product_name }}.
	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
{{ site.data.reusables.command_line.open_the_multi_os_terminal }}
3. Change the current working directory to your local project.
4. Initialize the local directory as a Git repository.
  ```shell
  $ git init
  ```
5. Add the files in your new local repository. This stages them for the first commit.
  ```shell
  $ git add .
  # Adds the files in the local repository and stages them for commit. {{ site.data.reusables.git.unstage-codeblock }}
  ```
6. Commit the files that you've staged in your local repository.
  ```shell
  $ git commit -m "First commit"
  # Commits the tracked changes and prepares them to be pushed to a remote repository. {{ site.data.reusables.git.reset-head-to-previous-commit-codeblock }}
  ```
7. At the top of your {{ site.data.variables.product.product_name }} repository's Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
8. In Terminal, [add the URL for the remote repository](/articles/adding-a-remote) where your local repository will be pushed.
  ```shell
  $ git remote add origin <em>remote repository URL</em>
  # Sets the new remote
  $ git remote -v
  # Verifies the new remote URL
  ```
9. [Push the changes](/articles/pushing-commits-to-a-remote-repository/) in your local repository to {{ site.data.variables.product.product_location }}.
  ```shell
  $ git push -u origin master
  # Pushes the changes in your local repository up to the remote repository you specified as the origin
  ```

{% endmac %}

{% windows %}

1. [Create a new repository](/articles/creating-a-new-repository) on {{ site.data.variables.product.product_location }}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {{ site.data.variables.product.product_name }}.
	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
{{ site.data.reusables.command_line.open_the_multi_os_terminal }}
3. Change the current working directory to your local project.
4. Initialize the local directory as a Git repository.
  ```shell
  $ git init
  ```
5. Add the files in your new local repository. This stages them for the first commit.
  ```shell
  $ git add .
  # Adds the files in the local repository and stages them for commit. {{ site.data.reusables.git.unstage-codeblock }}
  ```
6. Commit the files that you've staged in your local repository.
  ```shell
  $ git commit -m "First commit"
  # Commits the tracked changes and prepares them to be pushed to a remote repository. {{ site.data.reusables.git.reset-head-to-previous-commit-codeblock }}
  ```
7. At the top of your {{ site.data.variables.product.product_name }} repository's Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
8. In the Command prompt, [add the URL for the remote repository](/articles/adding-a-remote) where your local repository will be pushed.
  ```shell
  $ git remote add origin <em>remote repository URL</em>
  # Sets the new remote
  $ git remote -v
  # Verifies the new remote URL
  ```
9. [Push the changes](/articles/pushing-commits-to-a-remote-repository/) in your local repository to {{ site.data.variables.product.product_location }}.
  ```shell
  $ git push origin master
  # Pushes the changes in your local repository up to the remote repository you specified as the origin
  ```

{% endwindows %}

{% linux %}

1. [Create a new repository](/articles/creating-a-new-repository) on {{ site.data.variables.product.product_location }}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {{ site.data.variables.product.product_name }}.
	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
{{ site.data.reusables.command_line.open_the_multi_os_terminal }}
3. Change the current working directory to your local project.
4. Initialize the local directory as a Git repository.
  ```shell
  $ git init
  ```
5. Add the files in your new local repository. This stages them for the first commit.
  ```shell
  $ git add .
  # Adds the files in the local repository and stages them for commit. {{ site.data.reusables.git.unstage-codeblock }}
  ```
6. Commit the files that you've staged in your local repository.
  ```shell
  $ git commit -m "First commit"
  # Commits the tracked changes and prepares them to be pushed to a remote repository. {{ site.data.reusables.git.reset-head-to-previous-commit-codeblock }}
  ```
7. At the top of your {{ site.data.variables.product.product_name }} repository's Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
8. In Terminal, [add the URL for the remote repository](/articles/adding-a-remote) where your local repository will be pushed.
  ```shell
  $ git remote add origin <em>remote repository URL</em>
  # Sets the new remote
  $ git remote -v
  # Verifies the new remote URL
  ```
9. [Push the changes](/articles/pushing-commits-to-a-remote-repository/) in your local repository to {{ site.data.variables.product.product_location }}.
  ```shell
  $ git push origin master
  # Pushes the changes in your local repository up to the remote repository you specified as the origin
  ```

{% endlinux %}

### Further reading

- "[Adding a file to a repository using the command line](/articles/adding-a-file-to-a-repository-using-the-command-line)"