Closed branches: don't break if no new changeset in transaction
The `%d` in the revset used to analyse new changesets produces a hard error if the revno does not exist, instead of an empty result. We could later on try and introduce a logic similar to MR detection, but the topic is not always visible to GitLab anyway, for instance if the closing changeset is the only one, so that would require more changes. Meanwhile, we have a solution for one of the cases of heptapod#452
Loading
Please register or sign in to comment