While merging MRs with an explicit merge changeset, currently the web app issues two commands that change the repo
- hg commit (with the merge already prepared in the working directory)
- hg phase --publish
It would be better to be able to do both in one single stroke for performance (
hg startup is slow) and atomicity (always a good thing), but also because it's simpler. For instance, while working on #145 (closed), I'll have to explicitely disable sending GitLab hooks for the first operation (commit).
I've tried several configuration settings to do so:
phases.new-commit=public: not meant for this, but to got the other way round. The resulting phase is the max of the given one and the parents (the convention is secret > draft > public)
experimental.topic.publish-bare-branch=yes: like all settings meant to control auto-publishing, it doesn't react on a simple commit
Will probably have to convert this as a feature request or submission to Mercurial.