Closed adri326 closed 4 years ago
I'm seeing the same error. I'm running Debian Buster. I'm using fzf 0.21.1 though, not the Debian fzf. I'm using the Debian package for bc though.
I'm running git-fuzzy @ de1c13b8a5664541254278b7a6982b558847f20c and I am running into the same thing as the OP.
I am on a brand-new Arch linux install as well. I installed bc
but git-fuzzy status
still exits with code 1.
The issue I was having (fatal: ref refs/remotes/origin/HEAD is not a symbolic ref
) was I think because I had fiddled with the remotes configured on my clone and a fresh clone of my repo resulted in it working fine.
I opened #17 which I think is a reasonable action in the case the symbolic-ref is missing, but I look forward to hearing from @bigH if they think it is reasonable.
All of my primary repos were causing issuing this warning as well. Short of #17, I "fixed" it by just running git remote set-head origin master
in each of those to make sure that origin/HEAD
was pointing to origin/master
. (Ref https://gist.github.com/libitte/cbde168d26bc5faf9bf9fef648091b42)
merged the change. thank you!
I'm running Arch Linux, pretty up-to-date and fairly standard, running zsh and installed fzf through the community packages.
I had to install
bc
as a dependency, which wasn't mentioned anywhere. Additionally, I cannot rungit-fuzzy status
on any of the repositories I have cloned (including this one).On the repos I have committed in, the following error shows up, and
git-fuzzy
returns 1:On other repos, it just returns 1.