Error encountered on Source Tree - git log failed with code 128

[cyberpunkstudio]

When I clone a Git repo in Source Tree and make a commit and then go to Master branch to try and push my code to Bit Bucket, I get this error:

'git log' failed with code 128:'fatal: ambiguous argument 'origin/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

Please see screen shot:
https://dl.dropbox.com/u/119654/Support/Atlassian/Screen%20Shot%202012-10-09%20at%2016.39.03.png

This has been happening recently whenever I create a new repo and then initiate first commit. Seems to throw this error everytime. I'm not sure why as I haven't changed anything.

Currently running Mac 10.7.5 and Source Tree 1.5.4. and have Git 1.7.5.4 on my Mac.

[stevestreeting · Accepted solution]

Hmm, that's odd - it looks like something has happened to the definition of the remote branch 'origin/master'.

Can you try this:

• Click 'Fetch' on the toolbar
• Leave 'Fetch from all remotes' checked
• Check 'Prune tracking branches no longer present on remote(s)'
• Click OK

[cyberpunkstudio]

Thanks that fixed it. Not sure why that happened in the first place

[stevestreeting]

This kind of thing usually only happens if someone deletes branches from the remote, or forces a push which changes commits that someone else has pulled. Beause git fetches this from the remote and stores it, if it changes it can get confused unless you prune the remote info like this. You shouldn't need to do it normally.

[cyberpunkstudio]

Strange because, I only just created this new repo and no one else is working on it. I did the first commit and then it came up with that problem. There wasn't any remote branches setup

[Aravind Rangoju]

I still see this problem, I wasn't able to fix this by tip given by @Steve. Please suggest a workaround for this.

[eiger3970]

Hello, I still receive the error 128.

[serpulga]

I fixed by removing from bookmarks, opening the repo from File -> Open, and saving to bookmarks again.

[isral duke]

This helped me. Thanks.

[shooding]

Worked like a charm ! File -> Open is the key !

[Frédéric MARTINEZ]

Your upstream is gone.

Try this:

git branch --unset-upstream

[guntherfitzgibbons]

thanks - this fixed the issue

[serpulga]

This is happening everytime a delete a branch, even if I don't push it to a remote.

[Aran Wilkinson]

I am getting this issue, I'm using git flow and just finished with a feature branch, merged it into develop, removed my old feature branch and now get that error message everytime I change branch or load up the window with the graph it errors.

[Shane Parsons]

None of this worked for me... any ideas?

[Aravind Rangoju]

I still this problem, I wasn't able to fix this by tip given by @Steve. Please suggest a workaround for this.

[eiger3970]

I tried the Fetch thingy and also$ git branch --unset-upstream, but same error 128.