<div dir="ltr">Hello,<br><br>Currently, there are two "publish" fields, one in the task(regular "publish")-the scope is branch and not global,<br>and another under "on-success", “on-error” or “on-complete”.<br><br>In the current behavior, regular "publish" is ignored if there is "publish" under "on-success", “on-error” or “on-complete” [1].<br><br>For example:-<br>(a)<br>version: '2.0'<br>wf1:<br>    tasks:<br>      t1:<br>        publish:<br>          res_x1: 1<br>        on-success:<br>          publish:<br>            branch:<br>              res_x2: 2<br><br>(b)<br>version: '2.0'<br>wf2:<br>    tasks:<br>      t1:<br>        publish:<br>          res_x1: 1<br><br>"res_x1" won't be published in (a), but it will in (b).<br><br><br>We can either:-<br><br>1) Invalidate such syntax.<br>2) Merge the two publishes together and if there are duplicate keys, there are two options:-<br>   a) What takes priority is what's in publish under "on-success" or “on-error” or “on-complete.<br>   b) Not allow having a duplicate.<br><br><br>What is your opinion? <br>And please tell us if you have other suggestions.<br><br>[1] <a href="https://bugs.launchpad.net/mistral/+bug/1791449">https://bugs.launchpad.net/mistral/+bug/1791449</a><br></div>