Skip to content

Trigger merge status subscription when blocking MR gets merged

What does this MR do and why?

When a blocking merge request is merged, it affects the mergeability of the merge request/s it was blocking.

Since we need to update the merge widget in real-time, we need to let the subscribers know about it. To do this, we trigger the subscription whenever that happens.

How to set up and validate locally

  1. Enabled the realtime_mr_status_change feature flag so the frontend can update real-time.
  2. Create a MR (MR A) blocked by another MR (MR B) by adding MR B as a dependency.
  3. Open another browser window (window B) viewing MR A.
  4. Watch window B.
  5. On window A, merge MR B. The merge widget on Window B should update in real time.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #372642 (closed)

Merge request reports