Branch removal by obsmarkers
In case a whole named branch is removed by changeset obsolescence, the corresponding GitLab branch is not removed. As a result, the branch is lingering in the interface, and the Gitlab state file within the Mercurial repository has an entry for an obsolete changeset, which should not happen.
An example occured on this very project:
- I started the Heptapod 0.24 release branch as
heptapod-0.24
(that's a typo) - Later on, I realised the error and rebased the changeset, with the new, correct
heptapod-0-24
branch name.
Expected behaviour: the GitLab branch should have been removed, same as if the branch was closed with hg commit --close-branch
This has bad consequences, see hgitaly#102 (closed)