Can't update dotbot

This is probably a trivial problem, sorry for that. I can’t update dotbot following the instructions in the README. The current situation is:

~$ cd ~/dotfiles/dotbot
~/dotfiles/dotbot$ git status
HEAD detached at ef558f8 # This is the point when I first installed dotbot.

Now, the documentation says:

You can upgrade Dotbot at any point. If using a submodule, run git submodule update --remote dotbot

Indeed it seems to work:

~/dotfiles$ git submodule update --remote dotbot
Submodule path 'dotbot': checked out 'c29ba8d72224b545cbd7cf9446c3ed2ef13f8c24'
~/dotfiles$ cd dotbot
~/dotfiles/dotbot$ git show --summary
commit ef558f85d917c7d2fb52c17db10f0996ef92cb3f
Author: Anish Athalye <[e-mail]>
Date:   Mon Mar 6 15:11:02 2017 -0500

    Update dates

That was actually the last commit. But when I run ./install che old version is checked out:

:~/dotfiles$ ./install
Submodule path 'dotbot': checked out 'ef558f85d917c7d2fb52c17db10f0996ef92cb3f'
[...]

~/dotfiles$ cd dotbot
:~/dotfiles/dotbot$ git status
HEAD detached at ef558f8

The same happens if I upgrade with git fetch && git checkout origin/master (the other method suggested in the README).

What causes this is the git submodule update --init --recursive "${DOTBOT_DIR}" line in dotbot/tools/git-submodule/install. Am I missing something? How am I supposed to do a persistent upgrade?

[nagromc]

It is a good idea to include this extra step into the documentation.

However, I think it is not a good idea to update Dotbot every time install is run. It should be up to the user.

But including an update script would make Dotbot easier to use for more users. I like the idea.

[anishathalye]

Hmm, I don’t really want an update script, because it’s pretty easy to update using git directly. Plus, I think it would be weird to have the the update script make a Git commit on its own (and if it didn’t, then the update would be reverted on the next ./install).