-
Georges Racinet authored
Expecting the new payload sent by Mercurial, this performs an early treatment of published topics, before workers for each branch get spawned. In the most common case where the topic matches the target (named) branch, we don't need any repository access, so this is each and doesn't justify spreading with a worker per branch, as the general GitLab detection will do. The new HgManuallyMergedService takes care of updating the MR to the latest relevant topical changeset, to mark it as merged and perform all subsequent needed operations.
e5b0cd22f33e