Bookmarks do not get updated on pull if remote branch was force-pushed
I believe this applies only to the 1.0.0 beta.
The logic for detecting whether it's safe to update a bookmark on pull seems to be incorrect in the case that the remote branch was force-pushed. In this case, hg-git fails to update the bookmark and indicates that it's diverged.
What I'd expect is that hg-git checks the bookmark against the old changeset for the Git ref prior to pull. If it's the same, then it should be safe to move the bookmark to the new changeset for the Git ref. What hg-git appears to be doing instead is trying to determine whether the Git branch was fast-forwarded.