branch: don't let bookmarks shadow the default GitLab branch
We introduce a flag in the inner function that sorts out what to do of the branchmap entries, and use it for the default GitLab branch only. As the test demonstrates, the default GitLab branch will still point to the latest bookmarked head, which is consistent with what happens with "wild" multiple heads. This is a minor change of behaviour compared to the Heptapod standard, in which the default GitLab branch would not move in that case. The reason is that we don't have a natural support to store the previous position of the default GitLab branch. Of course hg-git based repositories have/had this extra state, in the form of the actual Git branch. The new behaviour is not worse and as much arbitrary as the previous one, and will of course be matched by py-heptapod's mirrorring to Git.
parent
9abda71b
No related branches found
No related tags found
Please register or sign in to comment