#Checkout in sourcetree full#
#Checkout in sourcetree code#

To verify that it is connected to the remote on GitHub, click the 'Settings' gear in the top right-hand corner and you should see the GitHub remote in the 'Remotes' section. Once that's done, you can double click the new bookmark and use SourceTree as you normally would. You can either clone it to a new location, or add the directory manually in the Local tab. Hold down the OPTION key on your keyboard to see the Generate Key button. Change the Protocol to SSH if it's not already selected. Click the Accounts tab, select the account where you want to add the SSH key and click Edit. Since this was just a test repo, I'll move it to the trash.)Īdding an Existing Repo that Has a Corresponding Remote to SourceTreeįor some reason if you click 'Clone' next to a repo you already have on your local machine and select the existing directory, it won't connect the remote repo with your existing copy. Creating an SSH key looks something like this: From the Sourcetree menu, select Preferences.

Select 'Delete' (When you do that, you'll be asked whether you'd just like to remove the bookmark from SourceTree and leave the repo on your machine, or also move the repo to the Trash.

#Checkout in sourcetree code#

LinuxServer: git init from 1 of the Source Code folders returned 'reinitialized existing Git repository in /foldername/.

LinuxServer: git status from the 4 Source Code folders returned a list of 'Untracked files'. Since this was just a test repo, I'll delete it from my machine. SourceTree: If I try to Clone a repository and enter the path to the 'clones', it recognizes them as GIT. If it doesn't, double click on the bookmark in the list in the 'Local' tab. The repo will be cloned to your local machine and should open in a new window when it's done. Name: (This is the name of the bookmark that represents the repo in SourceTree).

git checkout -b In Sourcetree first you need right click in the commit you want and select the Branch option.

This saves space with respect to multiple clones of the origin repo. SourceTree does not explicitly support the worktree functionality, but you can open each additional worktree in SourceTree and use it as a valid repo in its own right.

#Checkout in sourcetree full#

Switch branches or restore working tree files. This can give you mulitple working copies but without duplicating the full git repo locally. For apply or delete a stash you can use the Stashes menu in the sidebar.

Destination Path: (This is the location on your computer that you'd like the repo to be cloned to.) In Sourcetree for push a new stash you need select the Stash button in the top toolbar.

Source URL: (Leave this at its default.

Click the 'Clone' link next to 'My-First-GitHub-Site' (or the repo you'd like to clone).

I'll clone the 'My-First-GitHub-Site' to my local machine with SourceTree. Then create a BitBucket feature/release branch and in the subject to include this Jira issue key JRA-123 in remote Repo. Create an issue in Jira first like JRA-123, then get this Jira issue key JRA-123.

Now, you can click 'Clone' to clone one to your local machine. Note that the key has to be first in the branch name like this, JRA-123-My-branch.

Click the 'Remote' tab to see your repositories.Click the 'Gear' icon in the top right corner and select 'Settings'.If you do choose to use SourceTree as a GUI Git client, you'll need to add your GitHub credentials to SourceTree.