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

View change log for a single file?

Tai Lee Mar 06, 2013

I used to do this a lot in Cornerstone when I was working with SVN. Select a single file and then view the log. It would show me only changesets that affected the selected file, so I could quickly find out when a change was introduced and the surrounding context.

I can't find any way to do this in SourceTree. I've tried using blame on the file, then opening the changeset for the line I'm interested in, but once I do this I can't find any way to go back further into the history. When the actual change I'm interested in wasn't introduced in the most recent change to that line (e.g. subsequent unrelated changes, or code style changes), it makes it difficult to step back any further and find the change I'm interested in.

Am I just missing something in SourceTree, or Git itself that?

10 answers

1 accepted

28 votes
Answer accepted

Hi Tai,

The "Log Selected" option does just that. When looking at a commit, select the file, context click and hit "Log Selected". This works in both Git and Mercurial. (Correct me if I'm misinterpreting your post, though!)

Cheers!

Honza Zaloudek May 19, 2015

And is it possible to log file without needing to look for commit? Just view log of some random file from repository.

Like # people like this
Bruce Bowers Aug 14, 2015

I have this same question.

Doug Simon Sep 30, 2015

Me too. This is a very common activity and I'm surprised to see it's not a first class feature of the interface.

Saheed A. Oct 27, 2015

Would like to add my voice to the question asked by @Jan Zaloudek. Viewing a file's history, independent of commits, is a common activity so when will this feature make it into the next release of SourceTree?

Like Kateryna Shneidmillier likes this
Lawrence Dol Oct 30, 2015

Ditto to every one else. It's very common to want to see the changes to a specific file. Looking for a commit with the file is difficult and time consuming, especially if it's not been altered for some time.

Like Kateryna Shneidmillier likes this
Lawrence Dol Oct 30, 2015

Also LogSelected seems to limit the file to 100 changes/lines only so sometimes the changes are not all visible.

Brendan Levy Nov 19, 2015

Piling on. Would love to see this feature as well. We use Git for some non-code (documentation) projects as well and this would really satisfy our needs and is something surprisingly hard to find across the entire Git space.

Damien Sawyer Dec 08, 2015

... me too!! Very common workflow.

Andrew Finlay Jan 12, 2016

Why does it only log a files commits that occurred before the particular commit that you chose to log, even though there are newer commits available for that file on that branch? Is this intentional behaviour?

Ray Smets Feb 11, 2016

+1. Checking out the change history of any particular file would be awesome!

Lawrence Dol Feb 11, 2016

All, see my answer. Just make a temporary change to the file you want to log.

Like clement lenhof likes this
David Gunderman Aug 16, 2016

That's a workaround, not a solution.

Brian Oct 13, 2016

I agree that this would be very beneficial.  I should not have to make a bogus checkin, even if not pushed to look at the log for a file.

Henrique Rodrigues Nov 02, 2016

+1. "git log <file>" is a very important basic feature. It would be nice to see it implemented in SourceTree.

Marijn van der Zaag Dec 07, 2016

+1

Sebastien Pelletier Jan 29, 2017

+1 Can Atlassian acknowledge this issue?? Shouldn't be hard to add this feature!

dan moseley Feb 02, 2017

+1. I make a temporary edit to do this.

See my response below if you don't want to have to make a temporary edit.

Dmitriy Kazimirov May 09, 2017

+1

Kyle Delaney Jun 01, 2017

SourceTree shows a ... when there are a lot of changes. How do I see past that? How do I view the full log of a file in a single commit?

François Coupal Aug 10, 2018

I concur. I very often dig to find WHERE a particular file as changed, and why.

+1. Five years after the question, is this feature added to sourcetree?

Leanid Mendzeleu I'm New Here May 01, 2019

+1

28 votes

If you go to the 'File Status' view and change the pulldown which selects which files are visible -- it's normally on 'Pending' – to 'All files, sorted by path', then you can see everything whether or not it has a pending change.

You can then right-click on a file and do 'Log Selected'.

(This works on the Mac, anyway... can't speak for Windows)

 

Bruce Bowers Jan 04, 2017

Works for me on Windows. Thank you!

Robert Jurado Jan 13, 2017

Excellent, just what I needed.  A little complicated for a very common task

ryan ye Mar 16, 2017

Thanks very much, exactly what i need!!

Hamish Fawns Jun 03, 2017

How about files I deleted ages ago?

Adarsh Madrecha Dec 14, 2017

Perfect.

Dave Sky Jul 12, 2018 • edited Jul 20, 2018

This is some odd terminology for the commit history of a file (like "Annotate Selected" for "Blame"), and I initially saw the option but did not click it because I thought it literally does what it said in some SourceTree way, like "write some kind of log thing for this file".

I'm coming from command-line and Git Extensions in Windows, and the latter follows the terminology closely to Git documentation and intuitiveness, but SourceTree seems to be making their own terms and phrases for common things.

I don't understand; am I missing something here? Is SourceTree doing it right and everyone else is wrong, or does it need to improve its terminology and intuitiveness?

Jesper den Boer Jul 19, 2018

Thanks! I didn't know this.

Dave Sky Aug 13, 2018

I learned later that git-annotate was the command before git-blame caused it to be deprecated; why SourceTree uses the old term, I don't know.

2 votes
Gerald Leung Jun 12, 2015

Hi,

I am using SourceTree 1.6.14 on Windows.  I noticed the "Log Selected" feature only shows changes for the branch you are currently on.  Not sure if I'm the only one who would like this feature, but is there (or will there be) a way to view changes of a single file that occurred on all branches as well?  Basically the same as the SourceTree Log/History revision graph, but for a single file?

Thanks,

Gerald

Lawrence Dol Feb 11, 2016

See my answer. You can just make a temporary change to the file.

Gerald Leung Jul 13, 2016

Hi Lawrence, 

I'm not sure if I completely understand your solution, but I would like a full revision graph of a single file across ALL branches, not just the current branch I've currently checked out.  I've tried your method, but after making a temporary change to the file and then performing "Log Selected" it still just s

Lawrence Dol Jul 13, 2016

@Gerald Leung: Then my solution won't help. You'll only be able to see changes that have been merged at some point into the branch you are on. Sorry, man.

Andrew Hardy May 15, 2017

@Gerald

I have the same issue. My use case is that:

I find and fix an issue in a current branch of work and realize that I want to put that change into production as a hotfix.

I create a branch from the tagged release and then want to view *all* the history of the affected file so that I can cherry-pick the change into the hotfix branch.

Currently (2.0.20.1) once I'm in my hotfix branch and 'log selected' the history of the affected file doesn't include from 'then' to 'now' which is required to allow me to identify and cherry-pick the relevant commit(s).

1 vote
Lawrence Dol Feb 11, 2016

Right clicking on any file and selecting "Log Selected" is what you want to do.

But usually the challenge is to find a commit containing the file you want to track. The trick is to make a dummy edit to the file, and it'll show up in your Working Copy. From there you can right-click and log it (be sure to follow renames, since it seems to quickly get lost otherwise, even when no renames are involved, at least on the Windows version).

When you're done just revert your dummy change.

1 vote
Ray Smets Feb 11, 2016

Simplest way to do this:

On the command line in your project directory use the command 

git log --follow &lt;filename&gt;

Then use the SHA-1 hash to use the commit search feature in Source Tree (upper right corner). From there you can simply click "Log Selected".

Lawrence Dol Feb 11, 2016

Where <filename> is the full relative path from the project root.

1 vote
Deleted user Jan 13, 2017

Sorry to all the guys at Atlassian who have to review these posts, but I too would love to see this feature.  It would be my No 1 feature by a long way.

Best workaround I have found for anyone using Visual Studio is to enable Git as the source provider.  It sits nicely alongside SourceTree (neither seems to upset the other), and viewing a file's history in Visual Studio is simply a right-click away.  I use it all the time.

0 votes
Damien Sawyer Feb 11, 2016

That's a good workaround Lawrence.
I think that what's missing with SourceTree is a control displaying the full working directory as it was at any given commit.  Git Extensions does this (https://sourceforge.net/projects/gitextensions/). It's the killer feature that I would love to see SourceTree take on.

Gerald Leung Jul 21, 2016

I'm using "Custom Action" to launch Git Extension File History feature to do this.  It's better, but the revision graph doesn't show which branch the file belongs to.  Have you, by any chance looked into how to figure out the originating branch of an individual file in the Git Extension File History revision graph?

0 votes
Coto Aug 16, 2018

way to Hide this option man!

0 votes
Kenneth Kolano Dec 24, 2018

One other critical issue here is that the Log viewer doesn't provide a full list of changes, it seems to cut off after displaying the first 30 or so changes. That makes it impossible to review changes via Sourcetree.

0 votes
Siva Sundararaj I'm New Here Feb 04, 2019

It works fine. Go to "Log/History" tab and select "All files" and use any sort. It shows all the files irrespective of selected commit. You can then right click on the file and select "Log selected" to see history of changes.SourceTreeAllFilesLog.JPG

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted in Sourcetree

[dev team] Sourcetree for Windows 2019 Preview - Dark Theme

Hi folks, While the full post is over on our blog I'd like to share the dark theme we've got planned for 2019 here directly as well to keep the discussion going.  The ...

1,968 views 14 18
Join discussion

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