Here are some basic tips on cloning repositories, either your own or other public repositories.
If you are a collaborator on an Heroku app (ie. you created the app or someone added you) then you can access that apps code using the Heroku toolbelt. In the Code section of the Heroku dashboard are details on how to clone the repository using the
heroku git command. The
-a option is for specifying the name of the app you wish to clone.
For example, if you are a contributor on the sample-play-app, you would clone the Heroku repository using the command:
heroku git:clone -a sample-play-app
Once you have cloned the Heroku repository, you can use the usual Git commands.
To get the code from a remote repository, such as Github, we use a command called clone. This takes a complete copy of the Github repository, including all the history of changes.
The above command creates a link in your local repository to the remote repository. This link is given the alias
origin by default. So instead of refering to the cloned repository by its URL, you can use
So if you want to get updates from the remote repository you can use the following command:
git pull origin master
Here we are getting any updates from the remote repositories master branch.
You can see which remote repositories are linked to your local repository using the
git remote command in your local repository. The following command lists all the remote repositories, their aliases and their full URL:
git remote --verbose
You can also specify your own alias should you wish, either while cloning the repository or using the
git remote command:
git clone jr0cket
git remote rename origin jr0cket
When you clone a repository, a new directory is created using the name of the remote repository. So if your repository is called
sample-app-java then the directory created will also be
You can also specify the name of the directory the repository is copied into:
See the online documentation for Git Clone for more details