It seems like this would be easily achieved via a separate 'merge' button and/or a 'approve and merge' state (CI systems could then also set 'approve and merge' following a successful run on 'approve'). Alternatively, having configuration that allows a specific repo to be configured for 'merge when changes are approved' would mean that people who do not rely on 'approved' for CI workflow could benefit from this sooner rather than later.
It seems like this would be easily achieved via a separate 'merge' button and/or a 'approve and merge' state (CI systems could then also set 'approve and merge' following a successful run on 'approve'). Alternatively, having configuration that allows a specific repo to be configured for 'merge when changes are approved' would mean that people who do not rely on 'approved' for CI workflow could benefit from this sooner rather than later.