SourceTree considers pulled files as uncommitted c

Question

In some unknown cases when I pull using SourceTree, it consider all pulled files as uncommitted changes and won't allow to pull/push any more unless re-commit or discard those changes.

If I discard uncommitted files, it will discard all the changes have been applied by my team-mate.

What's wrong with that? Is there a known bug or whatever?

Answer 1

Not too sure if this is the issue but it sounds similar. When you pull, SourceTree pops up with a box. In this box there is a select box that reads.

Commit merged changes immediately

If this isn't checked the pull will can come in as an uncommitted change. It sounds like this is happening. By removing these files you are creating a delete commit.