In sourcetree, why can't I click on a bookmark and request a clone?
Asked by Kimball Johnson:

In source tree I can make bookmarks for branches. When I do so, I know Sourcetree knows the addresses of the remotes for that branch.

So, when a bookmark is selected, why can't I ask source tree to download a clone of the remote branch associated with that bookmark?

Or why can't I select a branch in 'log view' and ask Sourcetree to make a clone or get a local copy of the branch?

Why do I have to go to Bitbucket for this operation?

There must be some explanation for why this option is not in sourcetree.

I am not asking for a new feature, I want to know what technical aspect of GIT and its operation would be violated or what aspect of the state of a git repository prevents getting a clone or a copy of the working directory from Sourcetree when a bookmark or a branch for that repository is displayed in the Sourcetree UI?

thanks,

Kimball


Answers:
author: Seth
body: With Git, the primary repository is the local one. If SourceTree/Git were to allow you to easily clone a particular branch, it would almost certainly be cloning your local repository to a new, additional local repository.

Additionally, each time you clone a repository, the clone (as a fully-functioning repository itself) creates a copy of the entire history of the repository. Knowing this, it starts to become clear why it isn't common for people to regularly create multiple clones of the same repository.

If you want to work on two branches of the same repo in parallel, you want to create a [worktree](https://git-scm.com/docs/git-worktree). SourceTree does not provide any UI for creating worktrees (you need to use the command line), but once created, the worktree can be added to SourceTree like it is another repository. Keep in mind, since they share repo details, fetching in one will fetch for both, and the two worktrees cannot both checkout the same branch.


author: thinsoldier
body: Your window should look like this:

image2016-7-18 14:2:22.png  
[](https://community.atlassian.com/t5/Sourcetree-questions/In-sourcetree-why-can-t-I-click-on-a-bookmark-and-request-a/qaq-p/290422?attachment-id=10825){#link_1172b77bf41826}  
[](/tnckb94959/attachments/tnckb94959/sourcetree-questions/9006/1/image2016-7-18%2014%3A2%3A22.png){#display_1172b77bf41826_0}


author: thinsoldier
body: I can't see the commit column in your screenshot. If you actually can't see that column you either hid it or resized it to be too small to see.

Your screenshot means that particular commit exactly matches (based on your local copy's last know info about the state of the remote origin) the last commit on 2 branches on your origin: development and AST-649-bla-bla-bla.

I'm guessing you're diving into git on a big pre-existing project. If so, you should make a new empty project to experiment with git and sourcetree to understand better how git info is exposed in Sourcetree.


author: Kimball Johnson
body: Umm, I'm a little astounded by your answer....

Here's my description: "source tree has a display called a ***++log view++*** - each row represents a group of branches and/or commits (i guess that's what they are) all individually contained in their separate rounded rectangle"

I've attached the image: Kimball

This display is 'pretty common' in source tree.

So what are these 'rounded rectangles' meant to represent?

Is this a history? Are they pointers representing sequential 'somethings'? what would the somethings be?

Is there any relationship among them? Why are they all in the same row? Etc, etc...

Thanks,

[](https://community.atlassian.com/t5/Sourcetree-questions/In-sourcetree-why-can-t-I-click-on-a-bookmark-and-request-a/qaq-p/290422?attachment-id=3670){#link_1172b786e9817b}  
[](/tnckb94959/attachments/tnckb94959/sourcetree-questions/9004/1/2016-07-18_12-15-12.png){#display_1172b786e9817b_0}

comments: author: Seth
body: Each rounded rectangle represents a branch. A branch is a pointer to a particular commit that will move if a new commit is committed to that branch.

For more information, you might find the Git Book helpful: <https://git-scm.com/book/en/v2>

Focus on the first three sections of Chapter 1, and Chapters 2 and 3. (Chapter 3 especially for branching)