It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

checkout to different folder

I am a relative newcomer to Git and SourceTree but finding it extremely useful and powerful. My experience to date is with a centralized VCS and so I am hoping if I describe what I need to do someone can guide me as to how to achieve the same with SourceTree.

What I am used to doing, when trying to figure out where in a long list of changes a side effect bug may have been introduced, is to check out previous releases of the project to a temporary folder and use my file-compare tools to examine changes made. This does not seem like an approach that I can follow with SourceTree unless I am missing how to check out a previous commit to a temporary folder.

So, how does one do something similar with SourceTree?

Thanks for your patience with a newbie,

Sid

4 answers

That's very cool. I don't think SourceTree supports it at all yet - however, it is now distributing git 2.6 as the embedded version, so it should be usable from the command line as described above.

Here is a feature request for support for worktree: https://jira.atlassian.com/browse/SRCTREE-3204

Correct me if I'm wrong, but isn't it Git 2.15, not Git 2.5?  I don't even think there's a 2.2 release let alone 2.5 (at least not on Mac or Windows.)

You can also do a diff of two commits directly within SourceTree by control-clicking or command-clicking (depending on OS) on two commits.  The bottom part of the SourceTree window will then show you which files were added, deleted, or modified (on the left) and allow you to select an individual modified file to see the specific differences (on the right)

The only way I've been able to do this is to have two separate clones of the repository, and checkout different branches to each.

You can save a little disk space if your second repository is a clone of the first (local) repository, instead of cloning the remote a second time.

Just as a hint: Git offers a special command to localize the commit where a certain feature/bug was introduced - there should be no need to have multiple clones for this task:

git bisect

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Sourcetree for Windows - CVE-2019-11582 - Remote Code Execution vulnerability

A vulnerability has been published today in regards to Sourcetree for Windows.  The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...

4,917 views 0 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you