'git log' failed with code 128:'fatal: bad revision 'BranchName' '

[Shallow Thought]

Since deleting the local branch "BranchName" by right+clicking -> Delete BranchName, I get the above error message on every command I trigger from SourceTree. Everything seems to work though.

The branch did never exist on the remote and is deleted locally. Using git from the command line is working without complains.

git branch does not list the deleted branch. I "git clean -fd". "git log" also works with no issues.

System:

OSX 10.9.2

Sourcetree Version 1.9.4 (1.9.4) (update installed today)

[Shallow Thought · Accepted solution]

I could fix workaround the issue by:

- close Sourcetree window

- open Sourcetree Bookmarks view

- delete bookmark

- add bookmark again

[sangkwon]

It works as well.

[Jos]

Works. Thanks a lot!

[AAverin]

That's not a fix, just a temporary workaround.
Next time you switch branch and delete old branch this bug will appear again 

[g5coderswartz]

Doesn't seem to be working for me on Mac
Found this, which is a the right route for a permanent fix in the source https://jira.atlassian.com/browse/SRCTREE-2355 

[Patrick Leclerc]

It works for me too . Thanks you

[Greg Buresch]

Thanks this work around worked on Mac - OSx 10.11.6 & Source Tree Version 2.3.1 (69)

[Arjav Lad]

This worked, thanks

[AAverin]

This issue really needs a fix.

[Deleted user]

check the contents of .git/config  - delete the remote branch reference which no longer exists.

[chornsec]

I think that I have the same problem.

1. Have a repo where git status reports 'HEAD detached at tfs/default'

2. Add repository to Sourcetree

3. Double-click repository

4. Error encountered: 'git log' failed with code 128:'fatal: bad revision 'master''

[damien_friday]

I'm seeing this also. This should have been resolved long ago at this stage.

Should not be marked as solved.

[Jos]

It's march 2017 and I still have this issue 8-/

[Andrew McDonald]

This is still a problem in Sourcetree, and has been for years. I'm surprised it's still not fixed. The app just needs to switch the branch selection in the history view back to a different setting, such as "current branch", when the branch is deleted. It's also a huge problem when doing interactive rebases.

[Matt Collins]

I had this issue occur recently on macOS, in what felt like out of the blue, which lead me here.  

In case it's helpful for anyone else, one thing I did was run `git gc`, which gave me two errors:

• fatal: bad object refs/remotes/origin/[branch name]
• fatal: failed to run repack

The branch name here was the same as the 'fatal: bad revision [branch name]' error, so I figured they were related.  In my case, the branch name specified wasn't valid (or was no longer valid?), so I just deleted it.  Afterwards, I closed the SourceTree window and re-opened it to find it working again.

Weird. 

[Tessy Ahado]

I had the issue. In my case here is what I,Ve done to solve it.

CONTEXT:

It was related to certains type of files in my .gitattributes file.

The line filter "*.myext filter=lfs diff=lfs merge=lfs -text" in gitattributes file was added AFTER some ".myext" file were previously commited in the repository.

The ".myext" files were never been modified following the addition in the ".gitattributes" file.

SOLUTION:

- Clone the repository ( D:\My_Repo )

- Made a copy of all the content of the repository (excluding .git folder) in a temporary folder ( D:\My_Repo_tmp )

- Overwrite all the content of "D:\My_Repo" with the content of "D:\My_Repo_tmp"

- Commit and push to remote branch the changes detected.

OVERALL:

It forces git to push back the content that have not been pushed yet to LFS and regenerate the links to LFS.