Support reflecting MRs between services
Projects may have mirrors on multiple hosting services. On some services merge requests may not be able to be disabled and on the mirror, they are generally ignored due to it just being a mirror for primary developers. An action to "reflect" submitted MRs to the main repository with an optional message and status change on the mirror repository would help with this.
The fact that a given source MR has been reflected to a target MR should be stored in either the primary or mirror repository, but which one is better?
Cc: @brad.king