This is how I do it:
- go to Working Copy (at the top left)
- change the file filter from Pending to "All files"
- then either browse your repository or just type part of the file name in the filter text edit field at the top right. That filter works great as a way to drill down quickly on the file you are looking for.
- When you have found the file you want to know the history of: right click and select "Log Selected...", et vôila! :-)
The resulting list shows the dates the files was changed, who made the change, their commit comments, and of course a detailed breakdown of the exact changes.
Hope this helps.
Thank you for this detailed explanation – I would not have found it without the first couple of steps you described!
The UI may have changed a bit since you wrote this. For me, in SourceTree v2.2.4 (for Mac OSX), the first step was:
It's funny, I actually don't follow my own advice anymore. These days I do it as follows instead:
My other approach seems a bit overly complicated. Or is there a difference between the two I'm missing now?
To me it seems like making a change to a file so that it shows up in the list, then remembering to revert that change later (without getting it mixed in with other changes), is a bit more complicated. But I supposed it's easy enough to tell whether a change is insignificant (and it doesn't matter if you forget to revert it). Anyway, to each his own.
How about "show history" instead of "log selected" which means absolutely nothing to anyone who uses the product. I just spent way too long trying to figure out something that should be basic to the program because of ,IMO, poor naming convention. I hope you consider changing it to prevent future grief.
We're probably about to stumble on why it's "Log Selected". "Show Git Log for Selected Items" would be the correct, most self-explanatory term, but it's fairly long for a menu item. This thread is appearing for most Google searches for this misunderstanding/obliviousness so most people should get here and find the answer they need. If Atlassian want to take the feedback they've got it here already.
@Daniel Withams may be correct, but part of the point of SourceTree is for people not to have to learn the git command line interface. So in that sense it's not sufficient to match git experts' knowledge of git commands; it's important to match English speakers' knowledge of what words like "log" mean in English (as @John Featherlin pointed out: to log means to append information to a log, not merely to display a log).
Git's usage of "log" is a noun. SourceTree's usage of "Log Selected" turns the word "log" into a verb, which is bad UI design on Atlassian's part for the following reasons:
I agree with others that this is a defect in SourceTree.
"Show Log", "View Log" are good suggestions that stay with the Git terminology of using "log" as a noun.
I personally prefer "View History" that is typical in other source control software. I believe that this not be appropriate, as (I believe) that consistency - in the current context of Git - is more important than personal preferences.
If programmers are finding this thread and commenting on it, then hundreds of more people are also struggling to find this basic functionality.
I've been using SourceTree for years, and have been lamenting SourceTree's lack of a "View History" feature to other programmers. Now I have to adjust my lamentation to disclose this visual defect.
Atlassian, please take a few minutes to fix this defect.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
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