@abcdw There is nothing inherent to the mailing list driven workflow preventing this. This is something the CI could take care of. Having the CI being the one responsible for the merging itself ensures that
a) The main branch is always green
b) Any artifacts associated with commit are build _before_ the branch the commit is promoted to master