Skip to content

Mark merge request as unchecked when MR is prepared for mergeability

Patrick Bajao requested to merge 341681-prepare-for-mergeability into master

What does this MR do and why?

We currently only require a pipeline to be created (if there's any) before we mark a merge request to be ready for mergeability check.

Before this fix, we are also waiting for other stuff to be done before we set a merge request ready for mergeability.

In this fix, we split the logic in AfterCreateService so we only wait for the pipeline to be created. If it's done, we set the merge_status to unchecked.

This is behind the early_prepare_for_mergeability feature flag.

How to set up and validate locally

  1. Create a project with a simple pipeline.
  2. Open a merge request and wait for the pipeline to be created and the MR widget to show that MR is mergeable.

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 #341681 (closed)

Edited by Patrick Bajao

Merge request reports