Sourcetree not showing files that it's going to remove with a commit

[robertlagrant]

On SourceTree 1.7.0.32509 we're getting a strange problem, which is setting us back - when committing, we see the changes about to be committed in the usual way, code in the bottom right hand pane for each change listed in the staging pane.

However afterwards we see more changes were actually committed than were shown in SourceTree. The most damaging of which is it commits removes, even in folders that the person committing has never touched.

We first thought we solved this with Tools -> Options -> Git -> Show file changes from all sides of a merge, but it is still happening.

Is this a bug? Are we missing another option or view? We can't upgrade to the latest version because we are in an airgapped environment and Atlassian are no longer supporting that with the tool.

[Seth]

For uncommitted changes, there is a filter above the list. What value is selected in that filter? "All", "Pending", "Modified" are some popular options.

You probably want "Pending", which shows all files that have any status besides "Clean" (includes modified, added, deleted, conflicted, untracked, etc).

"Modified" only shows files that are tracked and have changes to commit.

[robertlagrant]

Thanks, I hadn't noticed that before! Which is the right one to see everything that's going to change in the repo? 

[Seth]

Edited the answer.

[robertlagrant]

Thanks Seth - problem is, Pending is the default, and that's what we've been using!