Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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.


OSX 10.9.2

Sourcetree Version 1.9.4 (1.9.4) (update installed today)

7 answers

1 accepted

21 votes
Answer accepted

I could fix workaround the issue by:

- close Sourcetree window

- open Sourcetree Bookmarks view

- delete bookmark

- add bookmark again

It works as well.

Works. Thanks a lot!

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

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 

It works for me too . Thanks you

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

This worked, thanks

This issue really needs a fix.

1 vote
Deleted user May 30, 2018

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

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''

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

Should not be marked as solved.

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

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



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.



- 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.



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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

7,273 views 5 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you