Why does Sourcetree allow switching of branches with uncomitted changes. The "git checkout" doesn't

Question

Sourcetree Version 2.1.2.5

I make changes in a branch, and forget to commit them (am new to git so haven't gotten into the habit).

I then use Source tree to switch to the next branch, which it quite hapily does.

I then find the code is exactly what it was with the other, uncommitted changes. Very confusing.

I then switched to the command line and tried a "git checkout" to the other repository and git wouldn't let me do it, saying there are uncommitted changes.

Why does Sourcetree allow it?

Dave

davet_nz · Answer

2.13.2.windows.1

Ana Retamal · Answer

Hi Dave, that's weird, for my previous example I used only the command line git, I was not using SourceTree. Which git version are you using? I have git version 2.11.0 (Apple Git-81).

Regards,

Ana

davet_nz · Answer

Hi Ana,

That is exactly the problem.

Sourcetree allows you to switch branches without committing your changes.  Git does not.  If at step 3 you try using command line git commands to checkout branch 2, it will not let you.

the git command and it's output is

C:\a_check>git checkout 02926D-A_add_comments_only
error: Your local changes to the following files would be overwritten by checkout:
db_objects/emp_change.pls
Please commit your changes or stash them before you switch branches.
Aborting

Sourcetree allows the checkout to 02926D thus confusing you over what changes are actually in the directory.

I did notice that if the changes are from a conflicted merge, Sourcetree will not allow the switch.

Dave