git: You are not currently on a branch about gpm

[xh3b4sd]

Thanks for coming back. I think it is a good idea to checkout the default branch, do the go get magic, and checkout the desired revision. I am not a massive fan of storing information about the default branch. Git for instance does that somehow. See http://stackoverflow.com/questions/18726037/what-determines-default-branch-after-git-clone. Not sure about svn, mercurial etc..

[pote]

That's weird! Definitely not intended.

Interesting: I just tested it on my local environment with gpm 1.4.0 and the same Godeps file as you, on first run I had no warnings, and on second run I have the same warning you are getting.

Behind the scenes gpm uses go get, coupled with the -u flag to fetch any updates that have been pushed to the repository between last time you updated it and now. When the dependency is in a detached head state we get warnings from git.

This isn't necessarily a problem: as long as the following line is present it means the commit you requested is in the local history and has been set.

>> Setting github.com/alicebob/miniredis to version bb985e34f0942b1d770bf96e87f830cf38804abe

Although... I do agree its ugly. 😅

Would it be worthwhile to add code to solve this warning? I'll think of a way around it, off the top of my head I can think about storing the default branch and checking it out before the update, or simply suggest deleting the directory and fetching it again. I could also simply delete it automatically, but I'm not big on deleting things without explicit user conscent.

What do you think?

[myusuf3]

Let's not go the delete route. What @xh3b4sd suggested in his last comment looks good.