Push dialog suggests invalid remote branch cache

Question

I'm using sourcetree1.8.1 on mac osx10.9.1.

Once I push commits to "forces" branch, and I remove remote branch "forces".

But sourcetree suggests "forces" branch repeatedly.

Is it cache? How can I remove that?

When I commit code with a option "Push commits immediately to: origin", commits are always going to "forces".

But it has only mater branch.

How can I remove "forces" auto selection?

Adam Kusmierz · Answer

It seems to be old problem, but have the same issue here, with 2.5.1 version. I grepped my .git directory for "forces" string, with no luck. Any other idea?

Seth · Answer

In the root of your repository is a hidden .git folder. Inside is a text file named "config" that should list all of your local branches and the remote ("remote") and branch ("merge") it is associated with. If your "forces" branch is not listed there, then SourceTree is probably caching something like you suspect.

Sangwook Song · Answer

Finally, I renamed local branch name "master" to "master2", and changed git>Push branch to "upstream".

Now when pushing master2 sourcetree set default push branch "master" correctly.

But when I renamed local branch name to "master" again, it suggest "forces".

I think sourcetree has invalid cache information inside somewhere.