atlassian-sourcetree

I've started using SourceTree and Git recently, but I am still confused about stashing/branching and my working copy files. I've been having trouble finding anything out there that clarifies things for me. My confusion is with regards to the working copy of files in relation to branches and stashes. The way I am expecting things to work is that my working copy of files will also be linked to the branch. If I am to switch branches, it will automatically stash my working copy before switching to the new branch. If I am to switch back to the previous branch, it will again stash the current

yesterday I could merge files in sourcetree with the external tool filemerge. Today, sourcetree wanted me to register me, and after my successful registration, I couldnt start filemerge. When I choose "Launch external diff tool" from the contextmenu of a file, 4 files appear (Backup, base, local and remote) but filemerge quits immediately. When I launch external diff, filemerge displays in the left /dev/null as source. How can I fix it? In preferences I choose filemerge as external diff tool. Have I to write the diff command for source tree manually, to give it the right local version of my

I know that similar question is already posted here, however I think that my scenario is a bit different. Here is what I have. I downloaded and installed the latest official version of the SourceTree software. Also, I have GitHub account with permissions to clone and push the repository. In order to manage a local copy I need to clone the on-line version. Here are the steps that I take: Start the SourceTree and navigate to File -> Clone / New ... In the opened window I paste the HTTPS clone URL . I copied it from the browser after I logged-in my GitHub account, so the link is correct. The nest

In SourceTree, how do I limit the log to only show commits that affected files within a given folder? I.e. the equivalent to: git log path/to/folder This Answer is Outdated This answer is now outdated. It was written before the Windows version of SourceTree had this feature built-in. The current version of SourceTree for Windows (1.5.2.0) has this feature now, so @bozi's solution should now work for both the Windows and Mac versions of SourceTree. Original Answer Instead of using SourceTree, you can use gitk -- folderPath to view the history of just the folder. gitk takes many of the same