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,
Since git 2.5.0 there is also the command
which allows to manage multiple working trees attached to the same repository.
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:
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot